Just released version 5.02 with lot's of (small) new features and a couple
bug fixes. Another really good release. I also did a major reorganization
of the files on my server to get ready for BoltWire CMS. Caused a few
hiccups on my end, but nothing that should affect you.

It's a long list: mostly new features, and a few bug fixes. The only thing
to be concerned about is I removed the archive and extract commands (and
their library functions) from the core. So if you use them, things could
break. I only use them on one very complex site and just decided they
didn't really need to be in the core. I can give you a plugin to restore
their functionality if you need them.

I also removed the pub directory and related vars from variables.php as I
have never, ever used this folder, and its not really connected to anything
in the core. If you use it for one of your sites, let me know and I can
give you the config.php lines you need to restore old behavior.

Normally I don't like to strip things out on short notice, but I'm trying
to finalize/stabilize BoltWire 5 soon, and I really kind of doubt any of
you use either of these.

On the positive side, I'm super thrilled with how the whole BoltWire CMS
system is coming along. I may release version 1.0 in a week or two...

Cheers,
Dan

PS. I'm posting a good bit more on the blog and there's been some
discussions in the forum--leading to a new bounty area you might want to
check out. Let me know if you have any troubles creating accounts or
logging in--as the community tools are still in a good bit of flux while I
polish things up.

CHANGELOG

* Added an auth bypass parameter to the mail function for use in plugins.
* Fixed bug in delete command bypassing abort messages.
* Fixed bug that blocked custom message overrides in input fields failing
certain tests.
* Slight fix to crypt parameter in form input fields, disabling it when no
value is entered.
* Bug fix in trim parameter for input fields, plus added mask= parameter.
* Added replace=true to explicitly allow limited field replacements in
input values--useful in hidden fields.
* Added two hooks to the new texttools function. One, in the iftrue
function for use in conditionals (including when) and the source function.
Both open up lot's of possibilities and required only a line of code each.
Plus, if we add new texttools, they become better available throughout the
system.
* Added a query= parameter to the list function as a shortcut for doing
something with info pages.
* Changed the register function to invalidate member id's that start with -
or _. Won't affect existing accounts.
* Include function has improved loop protection, so can show same include
in multiple zones.
* Added a $BOLTpluginAuth variable to allow plugins to enable specialized
auth lines to easily customize permissions.
* Small bug in auth conditional involving the find parameter. Also, fixed
BOLTauth function to show proper results for admins when checking
permissions on another user.
* Added a couple lines to engine.php to automate intelligent installation
of all core modules. Add loadCMS: false in config.php to disable this plug
and play capability for a specific field.
* Engine now correctly sets skin variable when skinpath is an alternate
location.
* In my relentless quest to keep the core trim, I deleted the pub folder
and all links to it in variables.php. I also moved the archive/extract
functions to a backup plugin. Let me know if you need this.
* Added an `{img} var to point to the shared/img folder.
* Can now set move site pages into a subfolder using site.folders by
defining its path in config.php. IE $sitePages = 'pages/site'; This is
needed so BoltWire can find the site.folders page (and site.config)!
* Several other small fixes...

-- 
You received this message because you are subscribed to the Google Groups 
"BoltWire" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/boltwire.
For more options, visit https://groups.google.com/d/optout.

Reply via email to