Like all software, BoltWire needs periodic updates. We are committed to providing security patches, bug fixes, and feature enhancements as needed. Plus, we are continually looking for ways to make our software even smarter. We log completed changes coming out in the next release on this page.
Our current focus is transitioning to version 7.0 through several significant upgrades designed to get ready for our Unleashed service. BoltWire 6.01 is mature and running smooth. To report a bug or request a feature, use our Support Area.
CHANGES IN THE NEXT RELEASE
The next release should be considered a beta for BoltWire 7.x. I have several significant changes I want to make, and I'm tackling them a few things at a time to help ensure a smoother transition. This release should be safe, but it's less about new features, and more about preparing for the next few releases. That is, upgrade with care.
- Changed the passdata command so that values passed via post mode, now show up as actual post variables available for use in scripts. Before was only available internally within BoltWire.
- Added an internal utility function is_stamp() to engine.php. Very useful for working with time.
- Added an optional "parts" parameter to the infopeek function to quickly grab one part of an info variable.
- Added a new "shortlinks" rule to the markup table. Now img:label.jpg and file:label.pdf both work as before. But I've added url:some.page and link:some.page as well, outputting a url or a hypertext link as appropriate. Note before the link: prefix defaulted to an img or file if it was an image or file upload type. This change could affect your links if you are using the link: on your site. If you are not sure, let me know and I could create a flag to revert to the old behavior and start flagging the old links as deprecated for a while to help you find them. I've always used the more intuitive img or file links. Note, also fixed a small bug with the file: prefix. I created these, by the way, for easy use in emails.
- Added one more shortlink syntax. Now re:somepage looks for an infovar "mypage" on info.redirects and if it finds it, will return a link to that page. This allows you to put "mypage: some.page.down.in.hierarchy" on info.redirects and give you easy shortcut links.
- The lines=true parameter in the source function is being flagged as deprecated in favor of vspace=true. This is to make it match the include function which used vspace=false to turn off line spacing. You can continue to use lines=1-3 in source function, which also matches the include function.