WebsiteBaker Community Forum
WebsiteBaker => General Announcements => Topic started by: Ryan on July 02, 2007, 04:37:47 PM
-
Hi all,
WB 2.6.6 was missing a file, so 2.6.7 has been released to solve this:
http://download.WebsiteBaker.org/websitebaker2/stable/2.6.7/
Thanks again to our Development Team for their great efforts 8-)
Ryan.
-
How to Update from previous versions
Upgrade from 2.6.5 to 2.6.7
Please use the changed file package from here and copy the files from this package over your existing files.
http://www.familie-gallas.de/media/File/WebsiteBaker-2.6.7_changed_files.zip (http://www.familie-gallas.de/media/File/WebsiteBaker-2.6.7_changed_files.zip)
Upgrade from all other 2.6.x versions to 2.6.7
Download the whole 2.6.7 package, delete the install folder and the config.php file from this package and copy all other files over your existing files.
Upgrade from 2.5.x versions to 2.6.7
This is the same as in the step before but you need an additional upgrade script. There exists a few versions on the download pages and here in the forum. Most of them didn't really work. If you plan to upgrade from 2.5.x, best is to send me a PM. I'll send you then a step by step upgrade info and the latest upgrade script.
Have fun
Matthias
-
Changelog, Fixes and new functions of WB 2.6.7
The main changes are:
- 100% UTF8 support
- Search works for all languages and special chars and includes a highlighting function
- New functions allow to have all .css and .js files in the template header.
A summary of all changes you find here:
Security fixes
- Fixed: The possible vulnerability described here: http://projects.WebsiteBaker.org/websitebaker2/ticket/376 (Changeset [420])
- Fixed: Reduced number of login trials from 50 to 3 (Changeset [432])
Bug fixes
Core Files:
- Fixed: WB now 100% works with UTF8 and all other Charsets. (Changeset [442], [454], [461], [464], [504], [510])
- Fixed: Some issus in search especially with special chars and html tags (Changeset [445], [468], [474], [476], [482], [486], [490], [493])
- Fixed: search result displays private and registered pages to not logged in users. (Changeset [480])
- Fixed: "Fatal error: Call to a member function on a non-object ..." messages produced from the search (Changeset [466], [470])
- Fixed: multilingual support to the search (Changeset [440])
- Fixed: intro page (intro.php) can now parse PHP-Code (Changeset [433], [434])
- Fixed: root_parent is not being set correctly in database (Changeset [447])
- Fixed: bug with settings2.php and page extensions (Changeset [499])
- Fixed: bug where error message not displayed when script fails to create a page (Changeset [501])
- Fixed: issue with Permissions for pages sections (Changeset [410])
- Fixed: issue with escaped single quotes in pagenames generation (Changeset [488])
- Fixed: private pages are visible for all registered user in admin interface and menu (Changeset [472])
- Fixed: bug makes it possible to delete WB Installation from Admin-Panel (Changeset [428], [430])
Form-Modul
- Fixed: Form modul stores empty records (Changeset [409])
- Fixed: Issues in search table entries (Changeset [415])
- Fixed: Wrong error message in form modul (Changeset [431])
News-Modul
- Fixed: Error when uninstalling the news-modul (Changeset [413])
- Fixed: Bugs in Newsfeed (rss.php) (Changeset [414], [495])
Menulink
- Fixed: Bug if you deleted a menulink page the linked page was also deleted in the pages directory (Changeset [444])
New functions
- Added: Added package which allows to integrate optional JS & CSS module files (frontend.css, frontend.js, backend.css, backend.js) into the <head> section of the HTML code. This allows developers to code modules which creates (X)HTML valid output. (Changeset [435], [456], [458])
- Added: New variable $module_description wich allows to have optional a language specific description of the modules in the language files of the modules. (Changeset [421], [439])
- Added: Search highlighting by simply adding the class ".highlight { background-color: #D0D0D0;}" to the screen.css of the templates (Changeset [437], [438], [445], [478])
- Added: JS framweork codepress to allow highlighting for JS, HTML and PHP code (Changeset [458])
What does the new functions do?
1. frontend.css, frontend.js, backend.css, backend.js
One of the main issues of the WB modules is, that the style informations are stored in the database and displayed in the body tag of the page. This gives a not (X)HTML valid output. The new functions can now be used to have all css and js of every modul in the head section of the template. The integration is very simple. You only have to do the following steps:
1. Add the following code in the head section of the index.php of your template
<?php
if(function_exists('register_frontend_modfiles')) {
register_frontend_modfiles('css');
register_frontend_modfiles('js');
} ?>2. Add to the modules a file called frontend.css
3. Copy the stylesheet definitions from the modul in the created frontend.css
4. Delete all stylesheet informations from the modul (database via options or hardcoded in view.php)
Thats all. Same works for .js files. Simply add a frontend.js to the modul wich includes the needed javascript.
But this is only the frontend part. Same could be done with the style for the admin backend. Take all styles out of the module files and store them in a backend.css or if javascript is needed in a backend.js file. This offers the ability for the users not only to easily style the frontend of the modules, they also can now style the backend. With the same functions it should be possible to make the whole WB admin interface skinable, wich will be a feature of one of the next WB versions.
2. $module_description
One other issue is, that if a modul is installed and you look at the Admin interface to the modul description this info is always in english, no matter wich language you use in your admin interface. With this new variable we have now the ability to translate the modul description. And as soon as the script find a translation he displays the translated info instead of the default english description. The use is also very simple. Every multilingual modul has a languages folder with the language files in it. To get a translated modul description simply add the follwing line to the language file of the modul:
$module_description = 'Here comes the translated modul description';
3. Search highlighting
With 2.6.7 we introduce the search highlighting. All needed code is included in the core files of WB. The only thing you have to do to get the search results highlighted is to add one class to the css file of your template. Feel free to define this class to your wishes. In the default templates we simple add a background color. You can also use other fonts , font weights or whatever you want. Please add the following class to the css file of your template:
.highlight { background-color: #D0D0D0;}
4. JS framweork codepress
This is also an option for moduldeveloppers. Possible things wich can be done with this:
If someone don't wanna use an WYSIWYG Editor and wanna write the content of pages as pure text, this code can be used for syntax highlighting. Also all other existing modules like "Template Editor" or "Modul Editor" could be rewritten to use the syntax highlighting. The Idea behind adding this to the core files is, that the code is only on one place and can be used from different modules without the need to put the code in the modul itself.
Matthias
-
Just upgraded, unzipped the package.. deleted the install folder and config.php and uploaded everything... went without any problems.
Slick work guys.
-
I just want to check...is show_menu2 part of 2.6.7 or does it still need to be installed?
-
@marathoner
show_menu2 isn't integrated in WB 2.6.7. You need to install it as modul like in the versions before.
Matthias
-
It's getting better and better. Great work. Thanks, guys!
Vincent
-
Big thanks to all developers. Update couldnt be easier. Works fantastic.
-
Upgrade from all other 2.6.x versions to 2.6.7
Download the whole 2.6.7 package, delete the install folder and the config.php file from this package and copy all other files over your existing files.
What about the Pages folder? Surely overwriting that would destroy all existing page files, or no?
-
The only thing in the pages folder is index.php, which is only there to redirect if someone browses to that folder.
There is nothing to "overwrite" your existing pages with, and it doesn't delete existing files when it "overwrites" an existing folder.
-
I have a question about the new function for putting CSS/JS in the head of the page. Is this for the purpose of site-wide use? I have a javascript function that I will require on only one page of the site... will the new function provide me that sort of access to the head when I create the page, or not?
P.S. Thanks to Panther for answering my previous question. I had assumed that uploading folders over folders was the same as working with individual files. Learn something new every day. :lol:
-
CSS and Javascript insertion is a way to insert per module the needed css and javascript
It is ment for module builders to place the css (and/or javascript) where it should (header section) instead of the body section (look at the form module, it will insert css styling in the body, since 267 it can be inserted neatly in the header)
Look at googlemap module where you need to put javascript in your template, with 267 it can be correctly inserted when a page with that module is called
Allso the css and js can be used in admin backend
In your case I think you need some javascript on a page.
Just copy your template (name-js for example) and put your javascript in there and use that template where needed
Good luck,
John
-
In your case I think you need some javascript on a page.
Just copy your template (name-js for example) and put your javascript in there and use that template where needed
I.e., a second template, differing only in the head section? Duh. I hadn't thought of that.
Thanks, John.
tim
-
thanks for the new release and the fixes guys :D great work and definately nice and easy to update from previous versions :)
-
I've updated a number of sites and all went smoothly. Very nice work, guys!
-
@rabsaul
I.e., a second template, differing only in the head section? Duh. I hadn't thought of that.
Another option is to add some logic to your template file that will load the javascript if the $pageid equals a certain page. The reason that I like this approach is that I'm constantly tweaking my template file and it would be tough (for me) to keep two or more template files in sync with the updates. Maybe something like this (not tested):
<?php if ($page_id == 14) {
echo "<script type=\"text/javascript\" src=\"<?php echo TEMPLATE_DIR;
?>/scripts/general.js\"></script>\n";
} ?>
-
Thanks, Marathoner... I certainly agree re having two templates makes updating a hassle. Your solution looks good, but I'm not really a scripter (I create my WB templates pretty much by way of copy and paste, and javascript is third party), so I doubt I could pull it off.
-
Ironically, I needed to use this idea this morning to incorporate some JS on a single page. It's pretty easy. Just cut'n'paste the following code into the <head> section of your template. Then change the $pageid from "5" to whatever the pageid is of your page needing the JS. Then change the location of the script from "/js/collapse.js" to the location of your script. Use the code below (now tested) as a starting point.
<?php if ($page_id == 5) {
echo "<script type=\"text/javascript\" src=\"/js/collapse.js\"></script>\n";
} ?>
-
You are the best new features rocks