WebsiteBaker Community Forum
General Community => Global WebsiteBaker 2.8.x discussion => Topic started by: pcwacht on May 26, 2010, 11:46:21 AM
-
installed a fresh svn 1364 and some things need thoughts
backend, settings -> advanced settings
1 - Module-order for searching: still filled with faqbaker,manual,wysiwyg
faqbaker and manual are non standard modules, no need to include them
much better to default to news,wysiwyg
2 - Section-Anchor text: is filled with wb_
better to leave this empty as default, hardly anyone uses this.
can't make this empty, it''l revert to old value
empty is needed to get rid of the anchorlinks in the output!!
Now phpmyadmin is needed
John
-
Hi John.
SVN is not a release. SVN is the floating develop environment.
1 - search_module_order is preset in install.php. This part is not touched yet.
2 - the mandatory setting for 'sec_anchor' is needed to generate valid anchor-id and anchor-name (must start with a alpha-char). This is to prevent 'normal' users without knowledge about naming s.o.. If somebody really wants to remove the anchors from final output, it can be done with a outputfilter-droplet using a simple regular expression like
<?php
$wb_page_data = preg_replace( '/<a class=\"section_anchor\" id=\".*><\/a>/iU', $wb_page_data );
return '';
?>
Insert this droplet somewhere in the mytemplate/index.php.
The droplet-tag will be removed and the output of WB is free of section_anchors.
Werner
-
1 - search-order
I know it isn't touched, I know it is svn. Being here a while!
Just saying it should be touched or thought about instead of not touching it.
2 - sec_anchor
You say, generate then use extra code for remove?
much easier solution not to generate the anchor at all is emptying the variable
you can't empty it with current svn, with 280 it was possible to save it empty, with svn 1305 allso
Allso I never get the idea of generating a valid anchor-id and anchor-name per section. Seem not needed in most cases.
John
PS
Glad you explained the working of a droplet to me :P being one of the authors :P :P
-
Other issue
backend -> preferences ->
username and emailaddress are saved in the db table users but not visible in preferences screen.
-
Hi John,
First tks for testing,
backend -> preferences ->
username and emailaddress are saved in the db table users but not visible in preferences screen.
i can't reproduce
with 280 it was possible to save it empty
Now again it can save it empty, if not empty it will be check of beginning with a letter
Dietmar