Vanilla 1 is no longer supported or maintained. If you need a copy, you can get it here.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
Options
cannot activate extensions
outbreak
New
i installed the new release of v1, downloaded all the awesome extensions i wanted to use, uploaded them to my server, and then tried to check the box to activate them. when i check the box, nothing happens and the extension does not activate.
what could be wrong?
edit: also it seems that the "you have not checked for updates" message will not go away after my updated install.
what could be wrong?
edit: also it seems that the "you have not checked for updates" message will not go away after my updated install.
0
This discussion has been closed.
Comments
If you check for updates and the message doesn't disappear, I'd bet dollars to donuts that your permissions aren't working properly.
Now, Vanilla is written so that it *should* catch those errors, but depending on different server settings and configurations, it may fail to do so (as it appears to be doing in your case). Typically I will put @ symbols in front of php functions that cause nasty error messages. That will allow the error to happen without reporting any problems. Then I'll check to see what the outcome of the function was by it's return variable or by looking at the $php_errormsg variable (Which contains the last error message to occur) and report a problem based on those. Sometimes those values don't return anything that indicates an error - and that is when things appear to work properly, but don't.
The offending code in this instance is in library/Framework/Framework.Class.ConfigurationManager.php:
function SaveSettingsToFile($File) { // Open for writing only. // Place the file pointer at the beginning of the file and truncate the file to zero length. // If the file does not exist, attempt to create it. $FileContents = $this->UpdateConfigurationFileContents($File); if ($this->Context->WarningCollector->Iif()) { $FileHandle = @fopen($File, "wb"); if (!$FileHandle) { $this->Context->WarningCollector->Add(str_replace("//1", $File, $this->Context->GetDefinition("ErrOpenFile"))); } else { if (!@fwrite($FileHandle, $FileContents)) $this->Context->WarningCollector->Add($this->Context->GetDefinition("ErrWriteFile")); } @fclose($FileHandle); } return $this->Context->WarningCollector->Iif(); }If you want to figure out what's wrong, the easiest way I can think of is to remove all of the @ symbols in that function and then go try to do an update check again. If the server encounters any errors when trying to write to the configuration file, they should be barfed onto the screen so you can figure out exactly what's going wrong.
"You are not running the latest version of Vanilla.
Because you are using a pre-release, all you need to do is download the Vanilla package and copy the new files on top of your existing files. You do not need to run the upgrade procedure on your installation of Vanilla.
You can download Vanilla from http://getvanilla.com."
Check your file permissions for the different directories and sub folders also check the owner of the files, if that doesn't seem to work restore your backup and go back to 0.9.2.6 and give Mark and the guys a chance to figure it out.