Calling All Zikulans,
You will be pleased to know we now have a a beta release of Zikula 1.3.0 from build 2313 (http://ci.zikula.org/job/Zikula-1.3.0/2313/). We need your help urgently to begin some wider testing and to get Zikula 1.3.0 out of the door.
THE PLAN
What will happen now is, after a beta testing period we will quickly move to a full 'code freeze'. We currently have a feature freeze on the 1.3 tree meaning we're not developing more features, but, since there is a lot of new technology, we're not freezing changes to those APIs to allow any deficiencies to be corrected. In practice, we're just being cautious so that the new technology is not only thoroughly tested, but implemented in several places to make sure everything is sufficient. Most of that work has been done, but caution says we need one more round of beta testing before we move to a full freeze, which means we can focus a release candidate and squash any remaining bugs.
PROGRESS
In terms of testing everything, including the new stuff, there's been some excellent progress and very high level of participation from module developers. I feel we need to give some special thanks to them because they have really gone out of their way to use and abuse the new stuff and as a result things have matured. As a result too, it seems several popular modules received a new lease of development life, like Content for example. Even already popular modules like News have also received unprecedented interest gaining new developers and contributors - I can site News as a shining example of this. The move to Github has added a new dimension to collaboration and naturally made the contribution process more open in all areas. I will refrain at this point from mentioning names because there are so many people who have made amazing contributions, but it's a real testament to the deep enthusiasm there is for Zikula especially when looking at all the 'new' people and the skills they have brought to the project.
When you look at Zikula 1.3.0 for the first time, you will be very pleasantly surprised. It looks better, it feels better and so many of the annoying things have been improved or removed.
THE DETAIL
In general, Zikula 1.3 should work with API compliant Zikula 1.2.x modules. It will not work with non-gettext modules at all. As most of you know Zikula 1.3 has a new module standard and API and "native 1.3" modules are a lot more efficient.
As far as I am aware, the follow list of modules are all "native" to Zikula 1.3 - even though there are Zikula core 1.2 versions available (with less features). You can find them all at Github. I would encourage you all to test out these modules and also report issues to each module's tracker (can be found at code.zikula.org). Github has a nice feature at each page ('Download') where it'll neatly create a zip of the development module (or tags). You can use this easily to grab the latest copy.
Clip - http://github.com/zikula-modules/Clip
News - http://github.com/zikula-modules/News
EZComments - http://github.com/zikula-modules/EZComments
Content - http://github.com/zikula-modules/Content
PostCalendar - http://github.com/craigh/PostCalendar
Multisites - http://github.com/zikula-modules/Multisites
Files - http://github.com/zikula-modules/Files
Scribite - http://github.com/zikula-modules/Scribite
OpenID - http://github.com/zikula-modules/OpenID
Legal - http://github.com/zikula-modules/Legal
Profile - http://github.com/zikula-modules/Profile
Pages - http://github.com/zikula-modues/Pages
There are many more, and there is a list at Wave of others - https://wave.google.com/wave/waveref/googlewave.com/w+XvI- g79A - understand that modules may not be completely up to date, so if you find any issues, please report then to the trackers for each project. (We will continue to use Google Wave until it's replaced by our own 'wave in a box').
We have all been waiting for the "New Zikula". Now we have something pretty amazing to show you all, but we need YOUR help to iron and polish the system - the sooner this happens, the sooner the final work to convert all modules to "native mode" can be done.
So I think I said enough. The more you help us (the development team), the faster we can reach a complete freeze and work to make a final release.
Download build 2313 from http://ci.zikula.org/job/Zikula-1.3.0/2313/ or try a later build, from http://ci.zikula.org/job/Zikula-1.3.0/. You might also want to try upgrading from Zikula 1.2 remembering the caveat about old modules (that dont conform to 1.2.x standards).
Report Zikula Core issues to the Zikula Core Issue Tracker
Lastly, if you have any feature requests or further ideas, please add them to the tracker and we'll see about assigning them to a future milestone. We're always listening.
Drak
--
Zikula Lead Developer
Board Member of the Zikula Foundation
Follow me on twitter.com/zikuladrak
Watch
GitHub Core
Show your support for Zikula! Sign up at Github account and watch the Core project!
GitHub Modules
Forum Activity
- craigh responded to »Using PageUtil::addVar() to load script code« 03:29 PM
- michiel responded to »password problem« 10:01 AM
- mazdev responded to »Hide "Register new account" and change template to 3 col« 07:50 AM
- mesteele101 created topic »Zikula 1.3.3 - Site Search 1.5.2 - Unable to turn off plug-ins« 07:48 AM
- mesteele101 responded to »ERR (3): E_USER_ERROR: Smarty error: [in pagesvar:pagesitem2en line XXX]…« 25. May
- mazdev responded to »Pages 2.5.0 and updating - Page not found« 25. May
- mesteele101 responded to »Zikula 1.3.3 - Selecting a category in Pages not working« 25. May
Zikula Blog
- Anatomy of Open Source Projects on Mar 07
- Continuous Review on Mar 01
- Not Invented Here on Feb 24
- How to Contribute Your Code at Github on Jan 13
- 10 Steps to Coding-Nirvana: Tips for Successful Module Writing on Nov 12
- Submitting Bug Report Tickets That Get Results on Aug 17
- Cozi Tricks #1: Syntax Highlighting on Aug 07
Login
Zikula 1.3.0 beta 2
-
- Rank: Software Foundation
- Registered: Jul 21, 2001
- Last visit: May 31, 2010
- Posts: 624
Posted: Jan 24, 2011 - 10:06 PM
-
- Rank: Softmore
- Registered: Jan 22, 2008
- Last visit: Apr 04, 2010
- Posts: 130
Posted: Jan 25, 2011 - 07:59 AM
There is no Modules module with the download - the link to the Modules Manager - index.php?module=Modules&type=admin gives me a page not found.
--
David
-
- Rank: Team Member
- Registered: Jul 15, 2004
- Last visit: May 27, 2010
- Posts: 277
Posted: Jan 25, 2011 - 08:09 AM
The module was renamed to Extensions.
Where did you found the link above? -
- Rank: Softmore
- Registered: Jan 22, 2008
- Last visit: Apr 04, 2010
- Posts: 130
Posted: Jan 25, 2011 - 08:18 AM
The link is from the administration top menu of the default theme - named Modules Manager
--
David
-
- Rank: Developer
- Registered: Aug 23, 2003
- Last visit: May 31, 2010
- Posts: 1428
Posted: Jan 25, 2011 - 10:25 AM
-
- Rank: Developer
- Registered: Jun 16, 2003
- Last visit: May 29, 2010
- Posts: 1967
Posted: Jan 25, 2011 - 10:29 AM
-
- Rank: Developer
- Registered: Feb 17, 2005
- Last visit: May 21, 2010
- Posts: 684
Posted: Jan 26, 2011 - 07:50 AM
I played around today with build 2315. I have to say everything works slick! Excellent work! Thanks to all involved
New installations seem fine. Sticking to the 1.3 supported modules I did not run into any problems. Unfortunately it was harder to test 1.2.x upgrades. I have hardly any sites not using Pagesetter ;). There was one that only uses Content, News, MediaAttach, Mediashare, menutree, Sitemap and Scribite. Trying to upgrade that site I did run into a few things:
- Database connection error during upgrade.php gives Blank Page in stead of error
- In upgrade.php link to upgrade documentation on left side did not resolve because some lang variable was not translated
- andreas08 theme directory is not overwritten by Andreas08 directory
- initialiy the administration module style sheets and JavaScript did not load causing tabs to show as unordered lists as well as JavaScript errors. After upgrading to the GIT version of Content that issue disappeared
- the upgrade created a few extra blocks which I found strange for an upgrade
- directory based short URLs loose extension (http://www.mapletulip.com/services.html became http://www.mapletulip.com/services)
- it was not clear to me what the upgrade process of modules to 1.3 modules was, I presumed modules should be upgraded after the core was upgraded?
In general the upgrade instructions were not completely clear, specifically section 2.2. I adapted it as follows:
Code
2.2 Prepare your existing installation
---------------------------------------------
i. if you use login by email address, you must change the login method to
login by username in the administration panel. You will be required to
login using your administation username.
ii. Before unpacking any files:
- Delete entire system/ folder.
- Delete includes/.
- Delete pnTemp/.
iii. Upload all files from the package you downloaded, copying over your files.
Manually edit the new config/config.php with your database credentials.
Note that the storage of database name, username and password has changed
significantly. Previously you would have three separate entries for the
database credentials, now you have one. It looks like this:
$ZConfig['DBInfo']['default']['dsn'] = 'mysql://dbuname:dbpass@localhost/dbname';
The values of dbuname and dbpass are no longer encrypted, thus make sure
you don't copy the encrypted values from your previous config.php, but look
up the original database username and password.
Be aware that there are more changes, so please make sure you merge in the
differences from the old config.php to the new one. Specifically pay close
attention to lines
line 26: $ZConfig['system']['installed'] -> probably 1 for an upgrade
of a working site
line 28: $ZConfig['system']['prefix'] -> must be the same as in your
original config.php
Do not change the following lines.
line $ZConfig['system']['temp']
iv. Make sure that the ztemp is writable to the webserver.
Please let me know if you want me to report anything of the above in Cozi?
Thanks again. Your work is highly appreciated! -
- Rank: Helper
- Registered: Dec 31, 1969
- Last visit: May 07, 2010
- Posts: 507
Posted: Jan 26, 2011 - 07:55 AM
I haven't checked it, but I won't be able to do anything useful unless Dizkus is functional. -
- Rank: Freshman
- Registered: Jul 28, 2010
- Last visit:
- Posts: 98
Posted: Jan 26, 2011 - 11:49 AM
Thank you for this amazing beta.
The git Pages link does not work. There is an l missing. By the way: On my test page Pages has problems with the new hook system. I will create a ticket for that.
I really like the new UI javascript functions. There is just one things I do not like. The UI images (e.g. window.restore.png) are loaded everytime even there are not used. -
- Rank: Team Member
- Registered: Apr 07, 2005
- Last visit: Jan 18, 2010
- Posts: 228
Posted: Jan 26, 2011 - 12:09 PM
phaidon - where did you found that issue with window.restore.png?
--
Polish Zikula Team
Bianor Works - my Zikula works on CoZi -
- Rank: Software Foundation
- Registered: Jul 21, 2001
- Last visit: May 31, 2010
- Posts: 624
Posted: Jan 26, 2011 - 12:55 PM
@phaidon - In short, 1.2 based hooks cannot talk with 1.3 based hooks or vice versa. You can neither configure them together nor can 1.3 based modules use 1.2 based hooks.
e.g. News + EZComments - there are both 1.3 and 1.2 versions. To use these modules together you need to use either the 1.2 versions, or the 1.3 versions, but not mixed.
Pages probably need a small refactor for hooks to 1.3 standards.
The hooks system in 1.3 is completely different and requires a new workflow. There is a completely different UI for them too. Since it would be confusing to both users to have a separate UI twice, and confusing to developers to have to code twice, they cannot be used together. 1.3 based modules will generate errors if the old hook calls are made. In the Extensions module, the old 'configure hooks' icons will only appear for 1.2 based modules.
Drak
--
Zikula Lead Developer
Board Member of the Zikula Foundation
Follow me on twitter.com/zikuladrak -
- Rank: Helper
- Registered: Dec 31, 1969
- Last visit: May 07, 2010
- Posts: 507
Posted: Jan 26, 2011 - 01:06 PM
Has anyone ventured into MediaAttach for 1.3? -
- Rank: Software Foundation
- Registered: Jul 21, 2001
- Last visit: May 31, 2010
- Posts: 624
Posted: Jan 26, 2011 - 01:16 PM
That has not been converted at all as far as I am aware. I think there might be efforts to write a new media module for 1.3 instead.
Drak
--
Zikula Lead Developer
Board Member of the Zikula Foundation
Follow me on twitter.com/zikuladrak -
- Rank: Helper
- Registered: Dec 31, 1969
- Last visit: May 07, 2010
- Posts: 507
Posted: Jan 26, 2011 - 01:34 PM
rewrite or not, the concept was great. Attach media to anything. -
- Rank: Software Foundation
- Registered: Jul 21, 2001
- Last visit: May 31, 2010
- Posts: 624
Posted: Jan 26, 2011 - 01:43 PM
Sure, it's an essential 'feature'.
Drak
--
Zikula Lead Developer
Board Member of the Zikula Foundation
Follow me on twitter.com/zikuladrak
- Moderated by:
- Support
