WebsiteBaker Community Forum
General Community => Global WebsiteBaker 2.8.x discussion => Topic started by: doc on February 24, 2008, 09:34:53 PM
-
Hello,
after 2 month of development, we are proud to announce that
the first release candidate of WebsiteBaker v2.7 is available now!
You can donwload WB 2.7 RC1 from the WebsiteBaker Project site (http://start.websitebaker2.org/en/introduction.html). Further information can be found on the WB 2.7 RC1 support site (http://start.websitebaker2.org/en/wb-2.7-rc1.html)
IMPORTANT:
The release candidate should not be used in an productive environment. Feel free to test the release candidate
on a local test environment like XAMPP.
Please use this thread only for reporting bugs which you may find. No feature requests will be accepted in this thread. This version already contains the features we would like to add with WebsiteBaker 2.7. Hence we will not add any new features to WB 2.7.
I would like to thank the developer team for making WB 2.7 happen:
Coding: Thorn, Swen, Ruebenwurzel, Doc
Backend Layout: Escpro
Have fun with testing WB 2.7 RC1
Regards Christian
ADDITION:
As we expect posts for many different areas regarding the WB 2.7 release candidate, we will comment in your thread, whenever we think it make sense. We will not modify your original text, but may add comments in brown font color. The author will be named in brackets e.g. (doc). Hope this helps to keep this thread readable.
-
hey there congratulations guys, the improvements are amazing :D i have it on a test environment online and its really smooth so far :) the extra little admin tweaks are brilliant and made WB even more user friendly...
spot on.. :)
-
I installed and run 2.7 on both of my PC's and think it's fantastaic.
Congratulations
-
The screenshot looks good - LOL. I'm a bit of a n00b I confess, so I won't be testing it. But - when it goes live, can older versions of WB be easily upgraded, or do you have to delete everything and start over?
The final release will have an upgrade script wich easily allows to upgrade from 2.6.7 to 2.7 (ruebenwurzel)
-
Design in admin panel is too swet for my. Older design was better. :|
-
Greetings!
Just did an upgrade from 2.6.7 to 2.7 RC1 and the only function I have under Admin Tools is Backup. I lost all other modules such Template Edit and Reload Modules. I obviously need Reload Modules to hopefully get what is there back. What did I miss? Have no idea if I can do a manual reload.
please read here (http://start.websitebaker2.org/en/wb-2.7-rc1.html) before upgrading (ruebenwurzel)
Any help would be appreciated.
Scott
-
Design in admin panel is too swet for my. Older design was better. :|
Hi,
First of all I would like to congratulate the team working on this release with what they have achieved. It works great. Had some problems directly after the upgrade, because the pages-section was empty and I thought I lost all the pages. But they appeared again in a fresh install of FF, so I guess this has something to do with the browsercache that needs to be emptied first.
The admin tools having its own section now is really a great improvement. The ability to have users in more than one group too. The same for the improved Captcha-features.
I do however agree with Nerjuz: the design looks a little cluttered with respect to the colors used. It's just a feeling I guess. To me it looked like the "old" version was a little more consistent in the color-scheme. For the rest it's just a matter of getting used to.
By changing two CSS files and optional about 4 template .html files and copy over the old icons, one can completely restore the old look and feel. Most likely we will offer the old backend style for optional downloads with WB 2.7 final (doc)
regards,
Erik
-
Yes!
This is a great job!
After testing on local which was very promising, now I installing and testing a small project on a live server.
Stefek
-
hello,
i'm using WebsiteBaker since 2005. i'm always amazed when a new version comes out. everything is where you expect it to be and every new feature makes live easier.
keep up the great work!
yours,
olli
-
First of all: congratulations! The developement team did a superb job. Great improvements which seem to work flawlessly (I did a clean install). Personally I like the admin tools as a separate section a lot, as well as its functionallity.
However, the design of the backend is not very appealing to my taste - it lacks the clearity that WB characterizes. (although I must say Ididn't like the old version either). If 2.7 is only a temporary version while we're waiting for 3.0 I'd say: don't waste time optimizing it. But if this release is going to stay with us for another year or so, I'd personally like to have a fresher, cleaner, more appealing user interface. By the way this also applies to the default template: it looks old fashioned and not very sexy.
All templates will be reworked in the final WB 2.7. The original layout proposal for the 2.7 backend can be found here (Ice blue admin) (http://www2.escpro.de/pages/downloads/freetemplates.php). However, the licencse of the icons was not clear (most likeley a kind of Creative Commons License not GNU GPL), therefore we decided not to use this icons for WB 2.7 (even they look pretty nice). (doc)
Vincent
-
Hi there all,
Just tested the new version and I like it.
I like the drag and drop of pages (it even works with Safari 2.04 on OSX).
But I noticed that drag and drop sections doesn't work with the same browser Safari on OSX.
A bug?
Edit: Tested drag-drop also with Safari 3.04 and now it works. So no bug but a shortcoming of Safari 2.04.
Just as Vincent I don't like the new look of the bakend. It looks a bit 'cheap' with ugly icons and colors.
I made myself, a log time ago, a different look of the backend with the same blue but with different icons.
@Vincent: is this what you mean with 'fresher and cleaner'?
Hello, for all backend layout related discussions, please use the thread opened by Bramus (https://forum.WebsiteBaker.org/index.php/topic,8809.0.html) - thanks (doc)
-
PLEASE NOTE:
For all WB 2.7 backend layout related discussions (https://forum.WebsiteBaker.org/index.php/topic,8809.0.html), posts etc. please use the thread opened by Bramus. This helps to keep readability while allowing an open discussion about layout - thanks.
Thanks for your understanding.
Regards Christian
-
First of all: The new version is very nice.
Some notices: When I´m selecting another language than english on install, some more settings under should be changed automatically, e.g. date format, time format and and charset. If your standard-language is not english, you have to make all the changes by hand.
Will be difficult to achieve for all languages, so this will most likely not be available in 2.7 sorry (doc)
What i´m missing too are some improvments in the media-section like preview, zip-upload.
Nice would be to change the owner of folders in the admin area. this would be very usefull for e.g. galleries, if you have to upload multiple-datas by ftp.
This would require some more changes and we will not include any new feature to 2.7. So maybe in 2.8 or 3.0. A forum member is writting a FTP module. In addition check out the tools listed on the help page, section knowledge base, article files and permissions. (doc)
-
Hi there!
Just a question: I know the coming v2.7 of WB (and RC1 already) come with FCKEditor instead of HTMLArea. I was just curious whether HTMLArea will still be included, or whether when I upgrade from WB 2.6.7, the old HTMLArea will be still available.
Since FCKEditor won't open very large websites, I can't do without HTMLArea.
Haven't found this question answered anywhere, that's why I posted here.
If you upgrade from an existing installation wiht HTMLArea installed, you simply need to set HTMLArea as default editor via the WB Backend. If you do a fresh installation, you need to download HTML Area from the Addons repository (http://addons.WebsiteBaker.org/pages/modules/wysiwyg-editors.php), install it via the WB backend and define it as default editor (doc).
Best regards,
VSG
-
I'm testing the latest version, and all I can say is: wow. Excellent work! I've done a lot of testing on my local machine and haven't found any serious bug yet, and will test it out on a live site later today (I do have a backup handy though, in case anything does go wrong, LOL).
Cheers!
-
Looks bloody nice - I'm still concerned about security and 777 permissions though. It's a pain to have to change them back and forward... is there something I'm missing?
Other thing for the less literate - the View text button has gone. I know there is a button for it but haveing the word there is useful for the less computer literate. So of whom may be on a learning curve with it.
Well done for all your hard work guys! :-D
-
Ah, wonderful! Eventually we have SMTP support integrated. And admin tools are easily accessible now. The form options offer the configuration of a receipt page.
Can't say much more right now, since I just installed the Rfc1. Upgrading from the previous WB 2.6.7 failed however, but I don't remember the error message, and simply deleted the older version.
The screendesign... well, I know, there's a separate thread 8-)
I will test and report if I have anything to report...
Thank you to everyone involved for your work!
Ayshe
-
I found an old problem in WB-27, which is easy to solve: Please make the News-textareas a little higher by default. I think für the teaser it should be at least 200px and the main textarea at least 400px. It is not practicable, when you can see only one line while writing in the teaser-area.
The changes are easy to make in modify_post.php on line 140 and 150.
Second: For my taste, the default-fckeditor-skin should be silver, not office 2003. Silver looks much cleaner.
-
Just installed 2.7 RC1.
First impression: Looking good :-D
Need to do some more testing but: Still looking good :-D
-
Nice work, I've been trying it for a couple of days. I don't like the new look admin CP. The colours are too bright for my liking. Other than that, keep it up!!
-
I think it would be nice if the "advanced options" are allways visible in the settings-menu. Now we have to push a button for the extra possibilities.
Or make an option if the webmaster would like the advanced options allways on or of.
If you want to make all options visible per default, simple remove all class="advanced" in the template /admin/settings/template.html (doc)
@Doc: It works with removing this CSS item. Thanks!
Luc
-
I have been creating and saving pages a lot, but often the page is not saved.
More specific while editing text an inserting images.
Also after saving the real website is returned.
I am testing on xampp.
-
I have been creating and saving pages a lot, but often the page is not saved.
More specific while editing text an inserting images.
Also after saving the real website is returned.
I am testing on xampp.
Are you shure you press "save" under the WYSIWYG section? Only this module needs to be saved. When you type a lot of text and insert many pictures AND then press another link (like the menubar) then your work is not saved! Keep that in mind. Or isn't that the problem?
-
Sure I press save. It happens when the word or the image I editted is still selected, before pressing on save.
-
I've found one problem with a site I set up, the script doesn't complete its run and finishes with the following:
Deleting field success_message from table mod_form_settings
Can't DROP 'success_message'. Check that column/key exists
Add default settings data to database for form section_id= 88
Database data success_page added successfully
Database data success_email_to added successfully
Database data success_email_text added successfully
Database data success_email_subje ct added successfully
Add default settings data to database for form section_id= 49
Database data success_page added successfully
Database data success_email_to added successfully
Database data success_email_text added successfully
Database data success_email_subje ct added successfully
Add default settings data to database for form section_id= 91
Database data success_page added successfully
Database data success_email_to added successfully
Database data success_email_text added successfully
Database data success_email_subje ct added successfully
Copying field email_to to success_email_from for form section_id= 88
Copyied field email_to to success_email_from successfully
Copying field email_to to success_email_from for form section_id= 49
Copyied field email_to to success_email_from successfully
Copying field email_to to success_email_from for form section_id= 91
The site admin still works and the site contents are accessible, but some tools are missing in the backend (the new admin tools link doesn't appear at all). Accessing the /admin/admintools/index.php link manually gives me an "insufficient rights" message.
As the above messages seemed to refer to online forms I am using on the site, I tried deleting current submissions and running the upgrade-script.php file again, but no dice.
Exactly, the upgrade script stops during updating your forms. All scripts wich comes after this (e.g introducing admin tools and reload modules, languages and addons) are now missing, so you have a instable system. The upgradsript for form is written for standard form modul of WB 2.6.7 (It should also work if you use the advanced from addons page) but it did not work with any other form moduls or patched versions from forum members or selfmade. To get a working 2.7 please comment out the form part in the upgrade script and run the script again. This should make WB 2.7 fully working except your forms, wich then should be upgraded/mad e manually. Hope you didn't try it on a live system, as the RC1 should only be used on testing enviroments. (ruebenwurzel)
-
Hi rueben,
No problem, it was a "test" site that I could play with. Nothing better to get an idea of how to update live sites later on!
-
I really like everything I see. The captcha as a site-wide secure addition is AMAZING. That was a huge problem for me before.
I have one suggestions which I've always desired for WB and it's not incredibly difficult.
EXAMPLE 1:
problem: I have 4 content areas on my template, I call them "header" "red" "tan" and "footer". They are each seperate content areas so the customer can customize their site. When they want to do this they hit edit and have to load a page with 4 FCKeditors! This takes a long time to load, slowing down their total editing time.
suggestion: be able to go from the "manage sections" page directly to the one section you would like to change. The top of that page would clearly label what is being edited, like: Page - Home; Section - "Header".
EXAMPLE 2:
problem: Same template as above, but, because each section looks identical when editing, they never know exactly which box they are editing. They might go and add a bunch of content to "red" when they really wanted it in "tan".
suggestion: add a label for each section so that it is obvious which FCK editor (or module) belongs to which section of the page. Hopefully, this info can easily be pulled from the info.php file of the template. Of course, if suggestion 1 is applied then this suggestion is irrelevant.
EXAMPLE 3:
problem: If suggestion one isn't applied, but 2 is, then we have a page with 4 FCKeditors each with a save button beneath them. If I need to make a change to each section, then I need to reload this entire page 4 times! This is a real time-waster.
suggestion: Is it possible to put one button at the very bottom (or top) of the page that says "Save All Sections"?
Overall, either break the sections of the pages out to be edited individually, or add labels for each section so they are clearly identifiable and add a "Save All Sections" button.
That's my 2 cents.
thanks for your ideas. But this thread here is only thought for testing 2.7RC1 and postzing possible bugs. Your questions are questions for additional features. Feature freeze for 2.7 was 01.02.08. so this will definetely not be part of WB 2.7, maybe in 2.7x or 2.8. (ruebenwurzel)
Understood! Feel free to move this post to the appropriate forum or delete if necessary.(mathetos)
-
not sure if this is strictly a bug but more of a feature implication, when i read about the page name changes i'd assumed it meant my nice search engine optimised page titles weren't going to destroy the usability of the admin area, however on closer inspection the result is my page titles (one of the most important seo techniques) are now translated as completely unusable urls. For example
My Shop - Selling all good shop things like hats, gloves and scarfs in the UK
That page title in a browser would be perfectly acceptable and search engine friendly. However results in the url
www.myshop.co.uk/My-Shop-Selling-all-good-shop-things-like-hats-gloves-and-scarfs-in-the-UK.php
Surely the menu title is more appropriate for the actual file name title as it's likely to be much shorter and to the point, in this case
'Home' equals 'www.myshop.co.uk/home.php'
All in all I love the new changes and bug fixes elsewhere, comments and captcha specifically, but this 'feature' is a really big problem I think, I'll definitely have to change it on every 2.7 site i do.
Sorry if this is in the wrong place btw and feel free to move it! :)
-
Just had a quick install, so I've not had too much of a play.
I think the admin looks fine, and I love all the little features that have been added. In particular the Admin-Tools and the Multiple User Group access.
One thing, seeing how your improving the user group access - could you please consider changing the user selection method? The current drop-down method is fine when you have a small number of users but larger sites with multiple groups and users make this method tedious.
I really liked the userstats mod, the way it displayed all users in a tabular format.
Something like this would be a great option.
-
not sure if this is strictly a bug but more of a feature implication, when i read about the page name changes i'd assumed it meant my nice search engine optimised page titles weren't going to destroy the usability of the admin area, however on closer inspection the result is my page titles (one of the most important seo techniques) are now translated as completely unusable urls. For example
My Shop - Selling all good shop things like hats, gloves and scarfs in the UK
That page title in a browser would be perfectly acceptable and search engine friendly. However results in the url
www.myshop.co.uk/My-Shop-Selling-all-good-shop-things-like-hats-gloves-and-scarfs-in-the-UK.php
Surely the menu title is more appropriate for the actual file name title as it's likely to be much shorter and to the point, in this case
'Home' equals 'www.myshop.co.uk/home.php'
All in all I love the new changes and bug fixes elsewhere, comments and captcha specifically, but this 'feature' is a really big problem I think, I'll definitely have to change it on every 2.7 site i do.
Sorry if this is in the wrong place btw and feel free to move it! :)
I agree, it is not a good idea to use page title as page name. Most people use long titles with keywords for SEO but page names look bad in that case, especially if site language is not English. I suppose the best solution is to have separate fields for title, menu title and page name.
Defenitely too late for WB 2.7. Maybe this becomes available in 2.8 or 3.0 (doc)
-
Hope i'm not too late with this, but the javascript (drag and drop for pages) could this also be done for the FORM module? I think it comes in very handy if you have to move something in the FORM. If you made a Contact page with about 10 textfields, and you have to move Adress 2 or something to the 3th place, then you are busy for about 4mins, with the drag and drop javascript it is a bit easier.
Hello, we will not add any new features for 2.7 just fixing bugs. This may make its way in one of the next versions (doc)
Hope it is easy to make this, and i think it is a great addition!
Good luck with the Final of 2.7 :)
-
First of all.. Great job done guys.
Installed on my test system without any serious problems.
The only hickup I had was caused by the fact that I always call my database something like wb-sitename. And there are no "-" characters allowed anymore.
I have already read something about that issue, and it is no problem for me.
I had one thing you could call a small "bug".
The fckeditor include.php is loading ../../config.php.
I am using the wysiwyg_edit module frequently. But loading the editor in the frontend, config.php has a different location. The better way (at least for me) is to change line 37 in:
require_once(WB_PATH. '/config.php'); This way it will always work correctly.
I can't wait for RC2.
Again, good job. WB is alive!!
Ruud
-
I have been creating and saving pages a lot, but often the page is not saved.
More specific while editing text an inserting images.
Also after saving the real website is returned.
I am testing on xampp.
same here unfortunately...
-
Defenitely too late for WB 2.7. Maybe this becomes available in 2.8 or 3.0 (doc)
Unfortunately we have to use long titles for search engines optimization, but such long page name is nightmare :-(
It is a really downgrade since 2.6.x... :-(
-
I have been creating and saving pages a lot, but often the page is not saved.
More specific while editing text an inserting images.
Also after saving the real website is returned.
I am testing on xampp.
same here unfortunately...
Do you use two windows (or tabs) the same time, one with backend, one with frontend - and with different Language-settings for Backend and displayed page, while this happens?
Answers in this thread, please:
https://forum.WebsiteBaker.org/index.php/topic,8949.msg52924.html#msg52924
WB2.7RC1: page isnt saved?
thorn.
-
I have to concur with the others regarding the page name issue. All of the other features are fantastic! And upon finding out that the page name issue exists I have unfortunately made the decision to stay at 2.6.7. I am sure there are others that are as disappointed as I am. :|
Is it possible to change that functionality through the template I am using? Maybe by calling a different variable?
You can modify three WB core files (Changeset 593 (http://projects.WebsiteBaker.org/websitebaker2/changeset/593)) to restore the old behaviour of 2.6.7 (doc)
Phil Parks
-
About: WB2.7RC1: page isnt saved?
Thorn,
I always use two tabs also with 2.6.7, and never had any problem.
Now with 2.7 RC 1 this is the first time pages are not saved.
It has something to do with the text or images being selected, or the cursor position.
Erik
-
I agree with the page title!=filename sentiment. While it was an interesting idea, using the full page title as the actual page name looks to be over-kill from what I've seen. Perhaps in some very hot search topics, it might be required, but I doubt many WB sites are in that type of market.
Using a fully-descriptive page title enabled some of my sites to gain enough page rank positioning. Having a well-chosen page name rather than a very long one is much more usable. Can you imagine the breadcrumbs for some sites for sub-pages?! :-o
The only spot where it might be worthwhile might be the news posts or perhaps individual product pages. Even then, there are elements that would be horrendous to have as part of the filename!
Thanks providing the 'fix' for this. I suppose having an option on the Page Settings would be possible, though more work and requiring yet another variable.
-
The only problem i found is that when i upgraded my site, the news page CSS giver me an error...doesn't save the changes i make...
I tested it first on me pc and worked great and now i use it on a online site as well...
seems to work great otherwise
-
The final release will have an upgrade script wich easily allows to upgrade from 2.6.7 to 2.7 (ruebenwurzel)
Just looked and I'm running 2.6.4 :-o How do I upgrade to 2.6.7 if that's possible?
Please look on our help page (http://help.WebsiteBaker.org/pages/en/basic-docu/installation/upgrade.php). (ruebenwurzel)
-
I don't know where to post this (here or in massmail modul threathttps://forum.WebsiteBaker.org/index.php/topic,564.0.html (https://forum.WebsiteBaker.org/index.php/topic,564.0.html))
I installed wb27rc1, show menu2, massmail and newsletter.
bud i get the following error message when i try to create a massmailpage:
Template Error: set_block: unable to set block list_block. Halted.
This error was reported some time ago. Unfortunatelly we can not reproduce it (not on Windows XAMPP nor on Linux LAMPP). Can you please provide some more information about your system configuration (server, file permissions ...) doc
I'm using standard round template. (have also tried 3 other templates without any luck)
Is it possible to use massmail in wb27 (i tested it in wb276 and it works without problems)
(i have search the forum and google without any luck)
-
Hello,
we have just released the second release candidate of WebsiteBaker 2.7 (https://forum.WebsiteBaker.org/index.php/topic,9001.msg53223.html#msg53223). Therefore we have closed this thread.
Thank you very much for all your feedback regarding RC1.
Regards Christian