OpenPublish 2.3RC1 is now available for download: http://openpublishapp.com/download
This release includes:
- A new editorial workflow system
- Rules integration
- Facebook "Like" integration
- Improved digital assets managements
- DocumentCloud integration
- Integration with an in-stream advertising network
- Editors’ Choice
- Improved and streamlined RSS export
- Tighter Solr Search integration
- Improved time management for Calendar Events
- Features and Context upgrades
- All modules upgraded to their latest versions
- Numerous bug-fixes
OP 2.3 includes a lot of new features. Most importantly an advanced editorial workflow system. OpenPublish developers spent significant effort to make the Drupal workflow module exportable (i.e. distributable) and create a default configuration. It's very fresh code and even though we tested it extensively, it has not yet been rolled back into the Drupal module. Considering this and the abundance of new features in general we are marking the current version as a release candidate for now.
Please download, test-drive and let us know if you find any problems. We will try to fix them and will release a final 2.3 at that point. Update instructions from 2.2 will be published with the 2.3 final.
Thank you
Comments
Default install on zend works
Default install on zend works fine.
I'll test out some features and revert back you.
Thanks in advance for all the hard work!
-Ronald
Should I rebuild the Indy on
Should I rebuild the Indy on 2.3 and fix the bugs as they are found, or wait until the final release?
I would wait, since update
I would wait, since update instructions are not ready, yet and there have been some major changes in 2.3 related to upgrade to and changes in Features and Context final releases.
.............................................
http://twitter.com/inadarei
i suggest you wait untill the
i suggest you wait untill the final...
If more bugs are found now, you have to update again.
-Ronald
Great job guys! New updates
Great job guys! New updates are always exciting.
I had an interesting situation when performing a fresh install. The first time, it crashed apache at this point in the installation script:
Remaining 78 of 139.
Installed Workflow module.
I deleted all the files, dropped the database, and tried again. The second time, at the same exact spot, my OS gave me the same warning that apache crashed. Oddly, it didn't actually crash this time. I was able to finish the install and everything seems ok.
But since it happened at the same spot I figured it was worth mentioning.
Also, I did have to bump the max_execution_time up. I guess 120 is no longer cutting it.
I'm sure it would be a huge pain, but maybe for 2.4 the install script should be converted to the Batch API. Just a thought. :)
@ksweet, it already uses
@ksweet,
it already uses batch API.
.............................................
http://twitter.com/inadarei
Will upgrade as soon
As the update instructions are published.
Digital Assets Management?
Any details on the improved digital assets management? I hope the way photos are cataloged can be improved some day.
Heh. That is exactly what it
Heh. That is exactly what it is.
When you use the imagefield (thumbnail image, main article image etc...) you could hit "browse" instead of just uploading file from disk, which provided image re-use for those fields, but you could not categorize files in folders from there. Now you can.
.............................................
http://twitter.com/inadarei
Some points
Hi Irakli,
I started testing and found the follwing so far:
page.tpl.php and page-front.tpl.php needs to be changed to reflect metatags.
You need to add:
<?php
print $head;
?>
just before
<?php
print $page_header;
?>
to make it work.
You also defined a maintenance page, which doesnt work.
First thing to do it to call it from settings.php.
Paste the following line below line 196:
Then, also edit maintenance-page.tpl.php:
Remove:
And add:
This is not the end unfortunately.....
Add the following to template.php as well:
function openpublish_body_class($left, $right) {
if ($left != '' && $right != '') {
$class = 'sidebars';
}
else {
if ($left != '') {
$class = 'sidebar-left';
}
if ($right != '') {
$class = 'sidebar-right';
}
}
if (isset($class)) {
print ' class="'. $class .'"';
}
}
And change the line called:
<body
<?php
print phptemplate_body_class($left, $right);
?>
to
<body
<?php
print openpublish_body_class($left, $right);
?>
That's the first things.
If you need clarification, just ask.
-Ronald
Some points
Hi Irakli,
I started testing and found the follwing so far:
page.tpl.php and page-front.tpl.php needs to be changed to reflect metatags.
You need to add:
<?php
print $head;
?>
just before
<?php
print $page_header;
?>
to make it work.
You also defined a maintenance page, which doesnt work.
First thing to do it to call it from settings.php.
Paste the following line below line 196:
Then, also edit maintenance-page.tpl.php:
Remove:
And add:
This is not the end unfortunately.....
Add the following to template.php as well:
function openpublish_body_class($left, $right) {
if ($left != '' && $right != '') {
$class = 'sidebars';
}
else {
if ($left != '') {
$class = 'sidebar-left';
}
if ($right != '') {
$class = 'sidebar-right';
}
}
if (isset($class)) {
print ' class="'. $class .'"';
}
}
And change the line called:
<body
<?php
print phptemplate_body_class($left, $right);
?>
to
<body
<?php
print openpublish_body_class($left, $right);
?>
That's the first things.
If you need clarification, just ask.
-Ronald
Some more points to consider
I tested with some content types that use OP Workflow and found that if you enable the "Publish" button it doesn't work.
It just stays in creation while it should go into "Published" state.
This happens with both the Article and Blog-item content-types (maybe some others, I haven't tested).
One more thing that should be enabled by default is a setting in the article content type.
On: admin/content/node-type/article/fields/field_main_image head over to File sources and auto-enable the "Autocomplete reference textfield" and do this as well under admin/content/node-type/article/fields/field_thumbnail_image
Due to OP2.3 having integrated Facebook activity, it;'s unnneccessary to include the FB button in the addthis widget. Because now you have FB links twice in a small window
If you need clarification just ask
I'll do some more testing later
-Ronald
Ronald, thank you for the
Ronald, thank you for the testing.
Can you, please, clarify what you mean by "enable the Publish button"? I am not sure I understand.
The AddThis widget exposes FaceBook Share button, while the new button we added is the Facebook Like button. They are not the same thing, but if it does not work for your website, you can easily customize the list AddThis exposes by overriding components/op-addthis-widget.tpl.php in your theme.
Thank you
.............................................
http://twitter.com/inadarei
With Facebook Like Button
With Facebook Like Button there is suppose to be a pop up that lets you share it on Facebook with comment "http://developers.facebook.com/docs/reference/plugins/like". But this is missing in the one added ya'll added. Is there a way to have share to Facebook also?
Never mind I got the share
Never mind I got the share feature working like I wanted
addthis setting
I find that the facebook addthis keeps linking me to my base url of the site, and not the relevant post.
Does anyone else experience this?
Help appreciated.
Nevos
Irakli, You have some options
Irakli,
You have some options when you create the node (say article):
- Creation
- Needs revision
- Ready for editing
- Ready for publishing
- Published
When you create the node and set it to "Published" straight away, it doesn't publish the node, but stays in creation state.
-Ronald
Ronald, I see what you are
Ronald,
I see what you are saying. I am not sure it's a bug, though. You are not supposed to publish content straight away (i.e. on the very first save). I mean, if you do that all the time - why even enable workflow for that content type?
I will admit, it is not necessarily an intentional design, but a side-effect of combining Rules with Workflow. This behavior can not be changed without losing important flexibility of being in complete control of which state is considered "published" (it does not have to be the last state, last state can be "archived" or something else).
That said, the existing behavior, even if slightly odd at first glance, sounds fair to me, for the reason that you should not be publishing content that is workflow-managed on the very first save.
.............................................
http://twitter.com/inadarei
Regardless of my long attempt
Regardless of my long attempt of rationalization, at the end of the day it was a bug (I love to be wrong) and it is fixed now, so should be fine in 2.3 final :)
.............................................
http://twitter.com/inadarei
$head variable problem (and
$head variable problem (and problem with the nodewords module) was solved in openpublish_code module code. No need to add anything to page.tpl.php and/or page-front.tpl.php. As a matter of fact, you should not add anything there because that will output head tags in a wrong location. The fix will be included in the 2.3 release.
Many thanks for helping debug it.
.............................................
http://twitter.com/inadarei
nodewords not showing openpublish 2.3
Hi Irakli,
If the change to resolve the nodewords issue was done after the release of 2.3rc,
and there hasn't been a release since then - what are the options to solve this issue?
wait for next release, get latest updates or use a specific patch?
Perhaps you could direct to the code in openpublish_core.mudule lines where the issue was solved.
Thanks!
Eagerly waiting for the new
Eagerly waiting for the new release with this issue fixed.
sTattler.com
re $head variable
Thanks for taking it into account!
Will await the release as usuall :)
CKeditor
Can CKeditor by default be updated to the latest version?
I have it running on OP2.2 with version 3.4.1 and node_embed and it runs fine.
RE workflow
Irakli,
Some people should be allowed to set it to published.
I can understand that someone who is hired you wouldn't want him to publish nonsense and want workflow to arrange that for you.
But for own people, they should be able to set it to published straight away.
In my own workflow rules in OP2.2 I have no problem in setting to publish straight away.
Wanna share your rule? :)
Wanna share your rule? :)
.............................................
http://twitter.com/inadarei
no rules...
The rule is that there is no rule :)
I have some handlings:
Create -> registered all
Review -> some people
Publish -> admins, redactional
Admins can create and publish straight away.
Ronald, but if you are not
Ronald,
but if you are not using Rules, how does Drupal know which workflow state = the one in which content should be published?
.............................................
http://twitter.com/inadarei
re workflow rules
Irakli,
In my view I have set that there must be a workflow state which then publishes it or not.
-Ronald
css input.form-text
One other thing that has some strange output is on the /user page.
I can see the following in components.css:
input.form-text {
border:1px solid #DADADA;
color:#808285;
font-size:1.25em;
height:17px;
padding:5px 3px 5px 5px;
Now in IE8 it displays (almost) fine, but in FF3.6.12 it's totally crap.
First image is in IE8:
http://www.altior.nl/ie8-op23.png
Second image is in FF3.6.12:
http://www.altior.nl/ff3.6.12-op23.png
After I change the height for the box it to 25px it's fine.
Maybe it's something the developers can take a look at as well.
-Ronald
Ronald, regarding that style
Ronald, regarding that style sheet, if you do not mind - can you please remove the "height: 17px;" altogether and see if the end-result is reasonable?
Thank you.
.............................................
http://twitter.com/inadarei
style sheet ok now
Irakli,
When removing the height it's fine in both IE and FF.
Just noticed (what i already changed in 2.2) that the same needs to be done for
div#search .form-text {
This is the search box.
You're welcome!
IMCE/File Browser upload
Hi Irakli,
I don't know whether this is a bug or made on purpose: After a new 2.3-installation the CKEditor-filebrowser is useless. There is no possibility to select an existing image in the database or to upload new ones for article illustration. The only thing working is to browse the files. In a 2.3-installation there is no upload-tab. This tab (http://docs.cksource.com/CKEditor_3.x/Developers_Guide/File_Browser_(Uploader) appears only after changing file browser settings (File Browser Type) from CKEditor from 'IMCE' to 'CFinder' - but it is not working properly. I was wondering why all these options are displayed in source code but don't work in the File Browser.
Discussion about upload-problems IMCE/CKEditor: http://drupal.org/node/714810
By the way: IMHO the order of fields for creating articles is quite unnatural. Wouldn't it be a good idea to have first the teaser field followed by the body field? The workflow for journalists is usually that they first write the teaser and then the main articles. By default in OP there is first the body text then 'Calais', 'More like this' options and then the teaser. I know that it is quite easy to change the order after the installation but it could be a good idea to implement this order in the source code.
Best regards
Andreas
Definitely a bug. Thanks for
Definitely a bug. Thanks for reporting.
.............................................
http://twitter.com/inadarei
Any word on the timetable for
Any word on the timetable for the official release?
I am to scared to update from 2.2 to 2.3 with instructions.
Timetable = when all critical
Timetable = when all critical bugs are fixed + update instructions are ready.
Hopefully next week.
.............................................
http://twitter.com/inadarei
Timetable
hi irakli,
do you have any news regarding the timetable for 2.3?
best regards
andreas
I'd like to know too
this has been out for more than a month. I fear you guys will release 2.4 before I even have 2.3 installed :)
Exposing CCK Fields after creating Event - OpenPublish 2.3 RC1
Hey Guys,
Excellent job on OP 2.3. I'm having an issue with added cck fields for an Event type exposed on the Full Page Node of Event (Front End). Can you help? or point me in the right direction.
CCK Fields that didn't show Price & Link..
http://www.golocalfun.ca/event/color-moccio
Thanks in advance for any help! - TK
Also, is the video available from San Fran Conference. The training on advance topics specific to OpenPublish. I'm willing to pay if necessary for it or documentation.
Using advanced features to customize your site:
Creating your own theme using the OpenPublish base theme
Using Context to build your site sections
Block placement using Context
Configuring OpenCalais and More Like This
Set up and configuration of Topic Hubs
menu
Irakli,
Maybe not so much a bug, but a feature request :)
In light of http://groups.drupal.org/node/105499 post, would it be possible to change the location by default to sites/all/themes/openpublish_theme/css/openpublish_theme.css ?