WebsiteBaker Community Forum
General Community => Global WebsiteBaker 2.8.x discussion => Topic started by: easyuser on December 28, 2013, 04:12:31 PM
-
Hi all,
signs are pointing to WB release 2.8.4. the next days. Finally. [This is no official post!]
You can get WB from here: http://project.websitebaker2.org/projects/wb28x/repository
Or from github (unofficially): https://github.com/cwsoft/WebsiteBaker/
Or directly from development SVN: svn://isteam.dynxs.de/wb_svn/wb280/branches/2.8.x --- or --- svn://isteam.dyndns.info/wb_svn/wb280
You can also get WB 2.8.4 as a .zip from an unoffical test site, set up with Rev. 2050 from 23.12.2013.
URL: http://testme.zweiwelt.com
Log in the backend and discover the new options:! You can create users / pages, upload modules and change whatever you want! Test WB 2.8.4 here:
WB-Admin: http://testme.zweiwelt.com/manager
User: testadmin
Passwort: testadmin
Known issue in WB 2.8.4 SVN rev. 2050:
- You can't create issues in news module
Please test here the hell out of it!
Especially following purposes:
- Delivered page modules: form, news, WYSIWYG, editors
- New page options: menu icon, page name, ...
- Languages: Frontend / Backend languages are different from WB 2.8.3. Please test them, and not only German / English.
- Security: Is backend really safe? Is a session only for logged in user? .....
- Compatibility: Are your modules working with WB 2.8.4?
- Environment: Change anything you like: Works on linux / Windows? With PHP 5.3, 5.4 and 5.5? Check the requirements here: http://www.WebsiteBaker.org/en/download/latest-version/requirements.php
- .....
Please let us know any bugs you discovered - here in this post! Please keep in mind that new features won't be in 2.8.4. Also have a look at this quote:
Note: The development of new features for the 2.8.x Series will be stopped at end of 2013 with the published release of WB 2.8.4.
New features from the future 2.9.x Series will not be migrated down to 2.8.4.
WB 2.8.4 will be supported with bugfixes and security patches in any case til the EOL at June, 30th 2015.
[...]
Attention: Feature requests will be moved to version 2.9.x of WB.
The current version is 2.8.4
This project includes any code from the beginning of WebsiteBaker in 2005 til EOL of WB-2.8.4 at June, 2015.
This project does not containing code from WB-2-9.x (started in Jan, 1st 2014) and up.
-
Can't (don't know where to) delete created pages.
-
Can't (don't know where to) delete created pages.
(i think)
its not allowed to delete pages in this testarea
the delete-function is the same like older wb's
-
Can't (don't know where to) delete created pages.
Yes, it's disabled to delete pages / media / users and so on for the user "testadmin".
Btw: You can't see groups you haven't created without being superadmin. :?
-
- Updated Argos-Theme in testsite to newest version from dbs - thanks. :wink:
-
- http://testme.zweiwelt.com/ updated to Rev. 2052.
Now the frontend registration / password lost etc. (/account-folder) should work in not English/German environments.
Only the email seems to be not send to the registrated person.
-
The testsite was updated to latest revision 2093, of course also all the downloads.
It seems, that all "bigger" bugs of the 2.8.4 are now solved - please test it again! :-)
-
- http://testme.zweiwelt.com/seiten/home.php Download was updated to Rev. 2096.
Of course you can download also from https://github.com/cwsoft/WebsiteBaker GitHub or directly from SVN http://project.websitebaker2.org/projects/wb28x/repository
Especially some small fixes like thumbnail / form captcha size were done.
Please test it, download it and install new in your test environment.
Also keep focusing on upgradings from 2.7 / 2.8.x sites, of course also here just in testing environments.
-
Hi,
just upgraded the WB 2.8 installation of a client to WB 2.8.4 REV 2101 and run into some issues I want to share.
The client gave me his admin backend account, but the "upgrade-script" failed. Jacobi22 pointet me in the direction of the super admin. Quick check in phpMyAdmin showed that the admin login of the client was not the super admin. After login as super admin, the upgrade script worked - also I needed to call it two or three times.
Apart from this, the upgrade from 2.8 to 2.8.4 went surprisingly smooth, especially as I had some "special" settings for the client, like changed /pages, /media/, /admin folders, old argos theme etc.
After the upgrade I found some smaller "issues", which I solved the following way:
Issue 1: Login into the backend as Superadmin throws a fatal error, while login with a account other than the super admin worked. Super admins gets greated by the following fatal error (most likely a test if they are the right person for the super admin job :wink):
Catchable fatal error: Object of class WbDatabase could not be converted to string in admin\start\index.php on line 108. A quick check revealed a typo in the line building the SQL statement in this line, easy to fix.
$sql = 'SELECT `value` FROM `'.$oDb-TablePrefix.'settings` WHERE `name`=\'wb_revision\'';
$sql = 'SELECT `value` FROM `'.$oDb->TablePrefix.'settings` WHERE `name`=\'wb_revision\'';
Issue 2: Three notices appear in the frontend related to already defined constants in Droplets (droplets.php line 48+49) and the output_filter (filterEmail.php line 23). The notices are related to the constants: OUTPUT_FILTER_AT_RE PLACEMENT, OUTPUT_FILTER_DOT_R EPLACEMENT and OUTPUT_FILTER_MODE. Quick and dirty fix was to explicitly surpress the notices by prefixing the define statements in the lines given by a @. Not nice, but the notices disappear.
Issue 3: The JavaScript encryption for email links does not work out of the box. In line 40 of the EmailFilter Droplet, there is a check if the mcdr.js function is included and depending of the results activates/deactivates the encryption. After changing the search string in the Droplet code, the email encryption worked again.
OLD: $search = '<script type="text/javascript" src="' .WB_URL .'/modules/droplets/js/mdcr.js"></script>';
NEW: $search = '<script src="' .WB_URL .'/modules/output_filter/js/mdcr.js" type="text/javascript"></script>';
Issue 4: The class .frm-field_title of the form module is not used to style the labels, but field_title. Added field_title to frontend.css to allow styling of this elements.
Issue 5: The contact formular does not parse tags added in the success message strings, so the output includes the tags. As quick fix, I removed the tags from the message text resulting in plain text output - not nice, but better than showing tags.
After these small hacks, everything seems to work. I didn't find the time for detailed search, just checked the functions my client needs on a day by day basis. All in all, the upgrade of the 5 years old WB installation went quite smooth.
Cheers cwsoft
-
@Issue 2 + 3:
WB 2.8.4 doesnt touch the registered droplets, so you use the old droplet code (i think, from WB 2.8.1, if i see the code lines) and WB doesnt need the old EMailFilter Droplet, it use the OutputFilter for that
the new EMailFilter-Droplet use only this Code (Code from the example-file
//:Emailfiltering on your output - dummy Droplet
//:usage: [[EmailFilter]]
return '';
Look into the Example-Folder from modules / droplets for the new version of all droplets
-
Hi,
WB 2.8.4 doesnt touch the registered droplets, so you use the old droplet code ... WB doesnt need the old EMailFilter Droplet, it use the OutputFilter for that
Ok, thanks again.
If not already implemented in the upgrade script, a short notice after the upgrade would be good informing that old Droplets needs to be updated manually.
-
If not already implemented in the upgrade script, a short notice after the upgrade would be good informing that old Droplets needs to be updated manually.
the problem is, that many people use (private) modified droplet-codes, but with the original-droplet name. if you implement the droplet upgrade in the wb upgrade, maybe you overwrite this private changes.
the code to install the droplets was a active part from the upgrade script, but its deactivated now,
a message about the install- or output-status was in this code-lines , i think, its simple, to put a new info-text in the active output ;-)
-
Hi,
and some more bugs (typos) in WB 2.8.4 Rev 2101 reported by MikeS in this thread:
http://www.WebsiteBaker.org/forum/index.php/topic,27075.msg186360.html#msg186360
Cheers
-
Hi,
I was looking for this thread yesterday, but somehow I didn't find it. I have started a new one here:
http://www.WebsiteBaker.org/forum/index.php/topic,27126.0.html
best regards,
Martin
-
Better would be a new tread, but I will put it here.
Was working a little with 2.8.4.
In the wb/admin/users/ section I had noticed a strange behavior:
When I assign multiple groups to an user.
Than, after taking a look at the code behind, I ended up not understanding nothing at all (sorry have my problems with classes).
Here my question:
Is there coding going on in the wb/admin/users/ part, to manage the user rights as they are managed in wb/admin/groups/ ?
Is there a ?new? mechanism in wb/admin/users/ that I do have to analyze a little more?
Asking, because if there is coding down the road, I will just wait and not schedule a hand out of the 2.8.4 as CMS.
Otherwise I would try to understand why the code is as it is.
And why the code of wb/admin/users/ is so different to wb/admin/groups/
Also, if no coding is planned I would check *if* there is a bug assigning multiple groups to an user.
Trying to be constructive, without rumzunörgeln MikeS
-
Still using WB 2.8.4 Rev 2101 and it works fine :-o
Why isn't this version released as stable???
-
Hallo
An der Version 2.8.4 wird nicht mehr aktiv gearbeitet. Die Entwicklerin arbeiten mit Hochdruck an der neuen WB Version 2.10.
Die aktuelle Version WB 2.8.3+SP7 ist die modernere Wahl in Punkto Sicherheit und Userfreundlichkeit.
Die Version ist voll php7-tauglich.
Im Forum gibt es Anleitungen wie man von Ver. 2.8.4 auf 2.8.3 +SP7 zurück kann, wobei es ein Fortschritt sein wird.
http://forum.WebsiteBaker.org/index.php/topic,29431.msg206445.html#msg206445
Googletranslate:
Hello
Version 2.8.4 is no longer active. The developer works with high pressure on the new WB version 2.10.
The current version WB 2.8.3 + SP7 is the more modern choice in terms of security and user friendliness.
The version is fully php7-compatible.
In the forum there are instructions as one from Ver. 2.8.4 to 2.8.3 + SP7, whereby it will be an advance.
http://forum.WebsiteBaker.org/index.php/topic,29431.msg206445.html#msg206445
-
Why should I go back from 2.8.4 to 2.8.3.SP7???
-
Why should I go back from 2.8.4 to 2.8.3.SP7???
Because the 2.8.4 series is not maintained anymore and the stuff planned for 2.8.4 and beyond has been integrated into the 2.8.3 series. So you can stick to 2.8.4 until you need to change something e.g. to work with future PHP releases, or to implement possible fixes for modules or core. As the 2.8.4 series is abandoned you will need to take care for it in the future. So the better choice is to migrate to 2.8.3 for medium and long term.
Cheers