Just one more question: I can't seem to find a download point (page/url) for the Xpack version of Boltwire. Could you let me know how to get to it?
Thanks. Jan On Friday, 5 August 2016 01:36:27 UTC+2, Dan wrote: > > Yes, I still plan to go through and separate the two back out again. It > won't really affect things particularly for users, but just makes > management on my end a lot easier. No idea as to the time table however. > Everything is working pretty good at the moment and I'm swamped with > projects so my motivation to go back and refactor the distribution is > small. Like they say, if it ain't broke, don't fix it. > > I may get to it before, but my tentative plan is to use the slowdown > around the holiday season to polish up and put out BoltWire 6. And will do > something different in terms of supplemental libraries for the XPack at > that time. If you need something specific sooner, please let me know. > Martin gave me some good ideas in terms of security, and I'm interested in > hacking around with them a bit. So I may just get back under the hood a bit > next week... > > Cheers, > Dan > > On Thu, Aug 4, 2016 at 6:36 AM TMurNGon <tmur...@gmail.com <javascript:>> > wrote: > >> Hi Dan, >> >> I was just wondering if you are still looking to release a refactored >> version of Xpack (as mentioned in your post above) and what your projected >> timeframe was? >> >> Thanks lots. >> Jan >> >> >> On Friday, 27 May 2016 00:00:52 UTC+2, Dan wrote: >>> >>> Just released a new version of BoltWire--that marks a pretty important >>> milestone. Namely, I've upgraded code throughout the entire script to bring >>> BoltWire into line with PHP 5.5 and above. Unfortunately, this release will >>> probably break sites relying on PHP versons below 5.3, but there just >>> wasn't any other way around it. For geeks out there, I've replaced all the >>> preg_replace functions using the deprecated /e parameter with >>> preg_replace_callback functions which are more secure. I also created a >>> custom BOLTpreg_replace function for the markup table. >>> >>> Because this upgrade affected so many systems in such a foundational >>> way, I can't guarantee there will not be glitches here and there. I've >>> tried it on several of my sites, and everything looks good--but there is >>> just no way to test every affected function. To be honest, I'm not going to >>> upgrade my live sites for a bit, just to see if anyone report a bug. I'm >>> reasonably confident about this upgrade, but I'm still flagging it as >>> quasi-experimental. On mission critical sites, you might want to hold off >>> till 5.12, just in case--esp if you have a lot of custom code. >>> >>> Other than the big system upgrade, this release mostly adds a good >>> number of advanced hooks for developers and some special features. I've >>> been working on all kinds of complex development projects, and >>> experimenting with alternate authentications systems, permissions systems, >>> installation structures, and more. BoltWire has held up really well to all >>> the challenges--just needed a few small hooks to expand its capabilities in >>> various really fun ways. >>> >>> I'm also deciding to change course on XPack program--and turn it into a >>> shared library you can add on to BoltWire, rather than a parallel >>> installation. It's easier for me to maintain a single code base. And I'm >>> personally running at least 3 separate libraries for different kinds of >>> projects. I suspect there are others out there running complex >>> installations with libraries too. Releasing the XPack this way will keep it >>> easier for you to manage those as well. Hope to have the revised XPack >>> (possibly a couple versions) ready in the coming weeks. Just need to sort >>> out and zip up! >>> >>> Enjoy my annual birthday release... :) >>> >>> Cheers, >>> Dan >>> >> -- >> 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 boltwire+u...@googlegroups.com <javascript:>. >> To post to this group, send email to bolt...@googlegroups.com >> <javascript:>. >> Visit this group at https://groups.google.com/group/boltwire. >> For more options, visit https://groups.google.com/d/optout. >> > -- 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 boltwire+unsubscr...@googlegroups.com. To post to this group, send email to boltwire@googlegroups.com. Visit this group at https://groups.google.com/group/boltwire. For more options, visit https://groups.google.com/d/optout.