Here's what went wrong: 5.1.29 introduced a minor template fix, half of which could be performed automatically and the other half of which was left as a manual change instruction. People who didn't apply the manual part had errors on the details page of 5.1.29 due to the changes being half-done. I rushed out 5.1.30 to automatically handle this situation so that people who didn't apply the template instructions wouldn't get errors... but, in my rush I didn't test that properly and it caused an error for everybody in 5.1.30. So now 5.1.31 fixes the fix of the fix. Sorry about that, I know it's not acceptable. I've added a check to the automated test suite to make sure the details page works before releasing in the future.
Comments on Error after upgrade
Forum Regular
Usergroup: Customer
Joined: Nov 27, 2006
Total Topics: 187
Total Comments: 465
Just upgraded to 5.1.30 and now get the following error on all link details pages...
Fatal error: Call to a member function contains() on a non-object in /home/hello211/public_html/classes/template.php on line 380
I am now going to do a server backup to revert back to the previous version otherwise my pages could get indexed by the search engines in that state.
Beginner
Usergroup: Customer
Joined: May 09, 2009
Location: ΛουτÏάκι, Ελλάς
Total Topics: 2
Total Comments: 8
Yeah me too the same error afer upgrade
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7867
This is fixed in 5.1.31 now.
Here's what went wrong: 5.1.29 introduced a minor template fix, half of which could be performed automatically and the other half of which was left as a manual change instruction. People who didn't apply the manual part had errors on the details page of 5.1.29 due to the changes being half-done. I rushed out 5.1.30 to automatically handle this situation so that people who didn't apply the template instructions wouldn't get errors... but, in my rush I didn't test that properly and it caused an error for everybody in 5.1.30. So now 5.1.31 fixes the fix of the fix. Sorry about that, I know it's not acceptable. I've added a check to the automated test suite to make sure the details page works before releasing in the future.
Beginner
Usergroup: Customer
Joined: May 09, 2009
Location: ΛουτÏάκι, Ελλάς
Total Topics: 2
Total Comments: 8
thanks Paul, fixed and efficent as ever