Posted by irakli on February 25, 2010 at 10:47pm
OpenPublish 1.7 has been released and can now be downloaded from: http://bit.ly/getop
There are many changes (listed below in more detail) compared to OP 1.6. We spent a lot of time thoroughly testing and documenting 1.6 to 1.7 update instructions: http://openpublishapp.com/download/op-1dot6-1dot7-update-instructions so we hope the update will be relatively painless for existing OP users.
The list of the major new features, includes:
- Most functionality moved to Features, resulting in significantly improved modularity and easier maintenance.
- Brand-new, more user-friendly Admin interface.
- Author extracted into a separate content type. Ability to indicate numerous authors per content item.
- Beautifully styled, Panels-based author pages.
- Ability to easilty schedule content for publishing.
- Support for Premium (e,g. subscriber-only) content.
- Improved navigation of connected content items (node references) using Node Relationships module.
- Improved multimedia support.
- Numerous bug-fixes.
Comments
With robust features support,
With robust features support, I'm back to being totally psyched on OpenPublish. Congrats, guys!
Followed all the steps.
Followed all the steps. Update seems okay with some minor issues. Only one warning came up and it says:
The selected file /tmp/file6A1fxd could not be uploaded, because the destination sites/default/files/js/gmap_markers.js is not properly configured.Another issue is that the first column on frontpage shows two "Featured Articles" headings. (site url: www.stattler.com)
sTattler.com
the gmap_marker.js error was
the gmap_marker.js error was related to permission of sites/default/files, which is now fixed by doing chmod -R 777 to files/
sTattler.com
Try running update.php and
Try running update.php and clearcache again. If the problem is not gone, uninstall op_misc module and re-install. If the problem persists and if you have access to the database, please run this SQL query:
UPDATE blocks SET title = '<none>' WHERE module = 'views' AND theme= 'openpublish_theme'Or, edit configuration for the "Homepage Featured Article" block (without enabling it) and set its title to "<none>"
One of those should work :)
.............................................
http://twitter.com/inadarei
Worked
This worked. Thanks.
sTattler.com
Nice work! 1.5 to 1.7
Great job all.
Just an FYI that I followed the 1.6 to 1.7 upgrade steps on a 1.5 site. So far the site is still working other than an array_merge_recursive() error as a result of op_article. I've disabled op_article and the error went away. Still trying to figure that out. Don't know if there are any other problems deeper in but so far so good.
I really like the implementation of features and context. Nice job!
Ok, a fresh install doesn't
Ok, a fresh install doesn't have that array_merge_recursive() error. However, we still have not solved the problems with Admin theme. The two bugs that I have found are the Theme Devel module disabling the Admin module's javascript. The second is the popup modal frame with the Node Relationship module. The Admin module should not show up in the child window and the css needs a little work.
Marine job board with Drupal 7 at http://windwardjobs.com
Admin menu gone! It's gone!
Yeah, I had that bug as well. Anyone know of a fix to make the admin menu reappear?
It's floating around in limbo out there somewhere.
This thing should still have a beta tag.
Theme Developer module
Theme Developer module breaking Admin2 is clearly a problem between these two modules and should be reported to their respective issue queues. Theme developer, while very pretty during presentations, is incredibly heavy and cumbersome tool in practice and we don't recommend using it at all, to be honest.
.............................................
http://twitter.com/inadarei
recoverable fatal error
This happens with only one user/author (myself :( ). When I click on the URL of this author, I get the following warning:
recoverable fatal error: Object of class stdClass could not be converted to string in /path/to/sites/all/modules/openpublish_features/op_author/op_author_layout/themes/views-view-fields--author-blogposts.tpl.php on line 21.sTattler.com
Can anybody please see where
Can anybody please see where the problem is in the following line? This is line 21 of the above tpl file:
<?php print l($fields['comment_count']->content . t('Comments'), 'node/' . $fields['nid']); ?>sTattler.com
I was able to recreate this
I was able to recreate this error and will put a fix in 1.7.1
Thanks a lot for catching/reporting.
.............................................
http://twitter.com/inadarei
Any changes in theme? Or
Any changes in theme?
Or maybe I should say any new tools to alter theme?
Minor changes
There have been some pretty minor theme changes, but theme improvements is the focus of our next release. We plan to make a better openpublish base theme that can be subthemed much more easily and provide a clearer separation between the data and the tpls to render it.
After disabling modules I got a blank screen
I was in the process of upgrading to 1.7 from 1.6, after disabling all of the contrib modules I was then going to upload all of the new modules to sites/all/modules. I hit save from the modules page, everything went blank. My guess is I accidentally unchecked a necessary core module?
But, I don't know how to get back to where I can select modules again. Any clue?
I'm not worried because I have everything backed up and I'm testing this upgrade on a local site, but if I can get this to work smoothly then I can just migrate this back to the live site.
Thank you,
Not sure why you were
Not sure why you were disabling contrib modules. I don't think that's a good idea (as in - will cause problems). I would strongly suggest to follow the instructions here: http://bit.ly/op1dot6update
.............................................
http://twitter.com/inadarei
I was following minor update procedure
I assumed that was part of the procedure. In the "HowTo: Updating Drupal 6.x to a newer minor version" (http://drupal.org/node/390448) it says to turn off the non-core modules. Well, stupid me for deviating off the documented path that you guys provided.
If nobody knows a way for me to get back, I'll just have to start over from my OP 1.6 install.
I don't want to sound like a
I don't want to sound like a jerk here. But that document also clearly states to fully backup the current system. This is a best practice and should always be part of a update/ upgrade workflow. I use the backup and migrate module to store the dumped databases on the file system and cpanel to download the home directory every once in a while and always before I install or update any module. Usually I just archive the directory and dump the database. Of something goes wrong I can restore the directory and then import the database in a matter of minutes.
Marine job board with Drupal 7 at http://windwardjobs.com
No need to preface the statement
I actually did back everything up and as I mentioned was performing this upgrade from a local install, so nothing was lost.
I was just trying to see if there was another way back so I wouldn't have to repeat the process.
Several times while building
Several times while building in Drupal I have experience the WSOD after enabling a module. Are you logging the PHP errors? If so you will probably find the error in that log. First, you can google the last part of the error to see if anybody else has had the problem. Second, you can use that error message when asking questions about the WSOD, it both allows the developer to know where and in what line of code the error occurred so they can debug or recreate the problem and it is a gateway for other Drupalers in the future to find information about that error via a Google search.
That being said, do you know what error was thrown?
If you already know this, then sorry, however, if a noob is reading this it's a good thing to know.
Marine job board with Drupal 7 at http://windwardjobs.com
Do i have to set it to log PHP errors?
If I didn't proactively set my site up to log PHP errors can I still access it?
I am a noob. Everything you guys post is helpful to me.
Thanks.
I still haven't figured out
I still haven't figured out to configure the logging myself. It does it automatically and put the messages in the error_log file the OpenPublish root directory. Perhaps, someone can explain how to best configure PHP error logging for OpenPublish which I sure is just the same as Drupal.
Marine job board with Drupal 7 at http://windwardjobs.com
@Signal, that was my guess
@Signal,
that was my guess that you were following the generic instructions, but i thought to ask. Disabling all contrib modules is an extremely blanket suggestion that actually works better for major version updates but not so much for minor ones. And it definitely is not a good idea for Features. Features modules dont like to be disabled unnecessarily because they define data structure and it can cause all kinds of problems. I honestly don't know why that page suggests disabling all contrib modules. Not such a good idea, in my experience.
In your case, the best would be to restore 1.6 from backup and follow the instructions for OP 1.6 update.
Thank you.
.............................................
http://twitter.com/inadarei
Got it working!
I did have a few errors along the way installing some of the modules; some of them were already a part of my previous install and for some I was a bit unsure which modules the list was referring to. For example, I could not find "advuser" on the modules page, I found "OP Advuser Config" instead.
Regardless, I got it all done and as far as I can tell it's working : )
Looks good!
Feeds is now working!
It turns out that 1.7 fixed the problem I brought up in a previous post concerning importing mp3s via RSS using the Feeds module.
I still do encounter one error right after the Feeds are "imported":
* warning: copy(http://hwcdn.net/n6g5e4u9/cds/shows/bmc/bmc060830a.mp3) [function.copy]: failed to open stream: HTTP request failed! HTTP/1.0 404 Not Found in /Users/joechoo/Sites/02_25_SCVBJ_test/sites/all/modules/feeds/plugins/FeedsParser.inc on line 148.* Cannot write content to /tmp/FeedsSimplePieEnclosure-bmc060830a.mp3
But thankfully, this is only something I see when I first import them. The audio nodes that are created as a result look great!
Should I be concerned?
No. It just looks like that
No. It just looks like that URL: http://hwcdn.net/n6g5e4u9/cds/shows/bmc/bmc060830a.mp3 is broken and that's why you are getting the error.
.............................................
http://twitter.com/inadarei
Hmmm. getting a php error.
The upgrade worked fine except for one thing, i get white page of death when i try and go to my artciles! Blogs,twitters,videos etc work fine.
I'm getting this in my apache logs:
PHP Fatal error: Cannot use object of type stdClass as array in /public_html/sites/all/themes/openpublish_theme/template.php on line 174,
Did you mean upgrade from 1.7
Did you mean upgrade from 1.7 to 1.7.1? I have the exact same problem after I upgraded to 1.7.1. My problem is mentioned here http://groups.drupal.org/node/53828#comment-149103
sTattler.com
This is now fixed with the
This is now fixed with the new build of 1.7.1 that you can download from OP website.
.............................................
http://twitter.com/inadarei
Ohhh yea. That's what I meant
Ohhh yea. That's what I meant 1.7.1. Thought I was in a different thread. Thanks for that link!
How would I downgrade to 1.7.0? My logs are LITTERED with all kinds of errors and I followed the instructions exactly. I wonder if a clean install would be better, and I could migrate the data over but i dont know what or how to migrate.
I don't know how to
I don't know how to downgrade, but overwriting is a possibility as there were no major changes. However, I would wait a day or two to see if they fix the problem. Otherwise have to go to back to 1.7.
sTattler.com
This is now fixed with the
This is now fixed with the new build of 1.7.1 that you can download from OP website.
.............................................
http://twitter.com/inadarei