Posted by irakli on March 4, 2010 at 11:21am
Download from: http://bit.ly/getop
OpenPublish 1.7.1 is a maintenance release for 1.7.x branch, it includes fixes to some issues reported after 1.7.0 release (e.g. Admin 2.x troubles with Node Relationships and errors on the author page) and it also includes new Drupal core with security update.
Update instructions from 1.7.0 to 1.7.1:
- Backup existing site
- Unpack 1.7.1 on top of 1.7.0
- Run update.php
- Clear cache.
- Check features and for overriden ones update from code. If you have modified Views and want to not loose your changes, review Features incosistences and only revert components that you are ok with (e.g. variables but not views).
Comments
Thanks :)
That is very nice to see. Although I had updated Drupal core yesterday, now this update has fixed the problem with author's URL (Ref: http://groups.drupal.org/node/52733#comment-147733). Thanks for being so prompt.
sTattler.com
I'm getting this error after attempting to clear cache
I keep getting this error after attempting to clear the cache.
Fatal error: Allowed memory size of 78643200 bytes exhausted (tried to allocate 2404051 bytes) in /Users/joechoo/Sites/02_25_SCVBJ_test/includes/database.mysqli.inc on line 303I've met and exceeded the recommended requirements, but still get this message.
• PHP version 5.2.x.
• memory_limit variable, in php.ini needs to be at least 92M, but 128M is recommended.
• If you are having problems (seeing "white screens of death" or errors during installation) try setting max_execution_time to around 120 and realpath_cache_size to 512K, 1M or even 2M.
Any clues?
Well, try setting memory
Well, try setting memory limit to 192M I guess, see what happens.
.............................................
http://twitter.com/inadarei
I actually have the memory limit at 512M
I actually have the memory limit at 512M.
I'm going to start over from my pre-1.7 install. I've been having major problems since I upgraded.
I should be able to follow the upgrade procedure from 1.6 to 1.7, but go to from 1.6 to 1.7.1 instead, correct?
Yes, and I can confirm that
Yes, and I can confirm that 1.7.1 installs on 128M limit, so it's weird you are getting these errors.
.............................................
http://twitter.com/inadarei
Fatal error
Some of my nodes are showing the following fatal error after I upgraded OP 1.7 to OP 1.7.1.
Fatal error: Cannot use object of type stdClass as array in /path/sites/all/themes/openpublish_theme/template.php on line 174The relevant block in template.php file is as follows. Middle line is line 174.
foreach($taxonomy as $term) {$out_terms .= '<div class="related-term">'.l($term['title'],'topics/'.$term['title']).'</div>';
}
sTattler.com
Some relevant information and more errors
I just tried to disable the devel module to see if that is causing the problem and found the following error:
Fatal error: Call to undefined function related_terms_links() in /.../sites/all/modules/openpublish_core/theme_helpers/node-article.tpl.inc on line 54When it comes to the template.php error, only "articles" are showing the error. Blogs and other nodes are fine.
sTattler.com
Ditto
Ditto or I got the same problemo!
I will get back to 1.7 until
I will get back to 1.7 until it is fixed. Need to fix it soon, though.
sTattler.com
How do you take it back to
I gave it up this morning, deleted the app and just finished putting it back up.
How do you take it back to 1.7
I downloaded and uploaded 1.7.1 from the OP site. I haven't run the upgrade yet to 1.6
It may be best to wait for the fix, since I'm not in a hurry. ----
New build #417 posted to
New build #417 posted to http://bit.ly/getop fixes the problem.
You can use it to re-update from 1.7.0, or overwrite "broken" 1.7.1 (in case you are wondering, template.php is the only file that changed in the new build from previous 1.7.1 build).
Sorry for the bug and thanks for reporting it.
.............................................
http://twitter.com/inadarei
Thanks!!
Thanks for the fix. It works. :)
sTattler.com
Just a quick note ----I use
Just a quick note ----
I use FileZilla for FTP. I had my settings pre-set to overwrite only, if the file source was newer
The old settings.php from 1.6 was not overwrite the new settings in 1.7, because it was older.
I've spent over an hour messing with FTP and finally realized I had to change that to OVERWRITE.
This is always a problem when you pre-configure settings in FTP.
Also, remember to change permissions on the settings.php file as well.
I hope this saves others some time.
My Primary Links Menu has disappeared
Hi everyone. When I upgraded to 1.7.1, my primary links menu no longer displays on any page. I have run update.php and cleared the cache and tried to hunt down where the template is that creates the HTML etc., but can't find it. The only thing I changed was to edit the template.php file to deal with the error generated by the related_terms_links issue that has already been identified (is that fixed by the way?).
I can go to admin/build/menu-customize/primary-links and add/remove etc. with no problem, but still no blue primary links menu shows up. All the feeds work and Calais is also working like a charm when I view a given article created. I have no other errors on my test site so far (except the related_terms error I mentioned above).
When I took a look at the page source, there is no html code for the menu, so it is not as if it is a browser issue, but more like something on the back end when the frontpage is being created for viewing.
Any ideas where to look?
Cheers
Had you changed theme in
Had you changed theme in 1.7.0 before upgrade (assuming you are using openpublish_theme)?
.............................................
http://twitter.com/inadarei
Just the openpublish_theme
No, I should have mentioned that, but no I have only been using the openpublish_theme. I had tried Tao at one point, but went back to the openpublish theme well before I did the upgrade to 1.7.1. Could there be some left over effects of having tried some other themes?
I tried today to change the theme from openpublish_theme for the 1st time since the upgrade to see if the theme was the problem and nothing would work - Garmin etc. Some error regarding the related terms problem. Not sure if that helps or not.
Any ideas how to get back my Primary Links Menu??
I have been digging around again today trying to figure out how I lost my Primary Links blue menu on top of my content using the OpenPublish Theme. Still no luck figuring this out. It is now becoming annoying to not be able to figure it out.
I also upgraded to 1.7.1-417, so now on the latest code base. That build fixed a few other niggly issues, but not my missing menu bar.
Anyone have any ideas on this?
Cheers
Can you post a screenshot,
Can you post a screenshot, showing what exactly is missing, please?
.............................................
http://twitter.com/inadarei
Screen shot of missing Primary Links menu bar
You can find the screen shot here. (need to go to the group's web page thread to access the link...)
You will see that the blue menu at the top is missing. I have been able to get the Primary Links to go in the header above the content through enabling the block in the Context for frontpage.
Cheers
Fatal error in admin theme (rubik)
Hi folks,
It seems like the following error is still happening in the admin section (we are using rubik which is the default admin theme in openpublish):
Fatal error: Call to undefined function related_terms_links() in /.../sites/all/modules/openpublish_core/theme_helpers/node-article.tpl.inc on line 54The following steps are required to reproduce the error:
We could work around it by copying and pasting that function from the openpublish theme to the rubik one (template.php).
Do you need any more information about it?
Kind regards,
Esteban
Same problem
I also get the same problem when trying to view any existing articles.
This after an upgrade to OP 1.7.1 build 417 from 1.6
I am using the newsflash theme.
Changing to the openpublish theme fixes the problem.
The offending code /in node-article.tpl.inc at line 54 is:
$vars['related_terms_links'] = related_terms_links($vars['node']->taxonomy);Commenting it out clears the error but I'm sure I do not want to do that?
I'm thinking I do not need the related terms functionality right now so...
http://satyamediagroup.com