Hi all, I've just released version 4.24 which was supposed to only be a transitional release before upgrading to version 5, but actually includes several new features, a nice bug fix and even a security patch.
But it definitely IS a transitional release--allowing you to get your site ready for a painless upgrade to 5. I've prepared a brief document here, to document how to do that: http://www.boltwire.com/index.php?p=downloads.4-5 I've also pasted the changelog below, which is much wordier. BoltWire 5 is scheduled to come out early next week. Cheers, Dan ---------------- *The Cutting Edge...* *boltwire4.24.zip <http://www.boltwire.com/index.php?p=downloads.go&v=4&r=24> May 21, 2015* Though this release includes several cool new features, a patch, and a fix--it is primarily designed to prepare your site for the transition to 5.xx. Be sure to install this version, then read this page for full instructions on how to transition <http://www.boltwire.com/index.php?p=downloads.4-5> to version 5. - Have long thought about adding the ability to use basic text tools from php, and finally decided to do it. In particular: length, substring, case, position, and trim. So can do <text substring=1,2>text</text> to get 'ex'. Can also mix and match, so <text substring=1,2 case=caps>text</text> to get 'EX'. Case can also be set to lower, first, or words. With length, <text length>Hello World</text> outputs 11. To trim, use <text trim> text </text> to get rid of the outside spaces. Use <text trim=t right>text</text> to get 'tex'. <text position=x>text</text> returns 3 (no 0 position), while setting position to z would return 0 (ie, false). - Fixed the random info extension (see the quotes plugin). Didn't realize it wasn't working before. - Added crypt=true to the list of parameters an input field can take to encrypt the value using the site cryptkey. Makes it easier to do password checking without having to use a separate plugin. - Fixed a small security patch in the exists conditional. - Changed the uploadTypes config variable to uploadImgTypes and uploadFileTypes. The defaults have not changed but if you have something custom in your site.config file you will need to update to these two new variables. They now work more systematically throughout the BoltWire system. - Fixed a bug in the data indexing mode when a data field has a null value. - Slight change in how the stopwatch feature is displayed (moving it into the body of the html page). - Updated the code to use both "when" and "if" in list and search functions. Also changed the deprecate flag to only trigger when "if" is used. This allows you to fix all the deprecated functions in your site without affecting site activity. Just examine each page listed on site.deprecate.if2when, change the if= to when= in your list or search functions, and then delete the page from the list after it is fixed. When the page remains clear and no longer triggers any functions, you should be safe to upgrade to 5.xx. In 5.xx the if parameter will apply to the function as a whole (as in all other functions), and the when parameter will be required for iterating through matches. - I changed the BOLTsearchResultsIfCount to BOLTsearchResultsWhenCount. If you are using that in a plugin or config file you will need to fix your code. - Similarly, I changed the deprecate flag in the inlist function to only trigger when find and list parameters are not set--so you can fix these conditionals before upgrading. After the upgrade all conditionals will go haystack > needle. So [if inlist 1 1,2] will change to [if inlist 1,2 1]. But since [if inlist find=1 list=1,2] works in both 4.24 and 5 you can fix these in advance and the transition to 5.xx should not cause any problems. Once again use the site.deprecate.inlist page to track down all instances of the deprecated markup and delete them one by one as they are fixed. Note the find parameter was introduced (replacing item) in this version. Item still works but will also be deprecated in 5.xx. - If you are using the BOLTCinlist function in a plugin or config you will need to update that function as well. Note the "inlist" utility function remains unchanged with the parameter order remaining item, list. - To fix pages in site.deprecate.insource, change markup like [if insource string='...' find='...'] to [if inline line='...' find='...'] and mark off the deprecate page. The string parameter will be removed when we move to 5.xx and the new inline conditional required instead. - When searching for deprecated markup in the specified pages, remember that they can show up in other places beside the page itself--such as an included page or a search template. Some can be a bit tricky to find. Also if the item or list has the potential of being a null value you should use quote marks (ie: item='') to avoid triggering the deprecate flag. If you can get to the point there are no more triggers, there's a good chance the upgrade will go smoothly. Also, if you don't have one of these site deprecate pages, then you have nothing to worry about with 5.xx. It is probably because you don't use any of the code being deprecated. That is--assuming you haven't turned the deprecate feature off in site.config. :) -- 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.
