Re: BoltWire 5.11

[John Morris]

Thanks Dan, we are running php 7.0.22
Appreciate the speedy reply!
John

On Monday, August 21, 2017 at 4:04:25 AM UTC-7, Dan wrote:
>
> Yes, we have a problem with BoltWire not running on php 5.5 and up. Do you 
> know what version you have. We know what the issue is just haven't quite 
> fixed it yet.
>
> Cheers
> Dan
>
> On Mon, Aug 21, 2017 at 2:59 AM, John Morris  > wrote:
>
>> Hi Dan, 
>>
>> I too seem to be getting that pesky 500 internal server error, are you 
>> still offering help on this? Thanks sir
>>>
>>> John
>>
>> -- 
>> 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 .
>> To post to this group, send email to bolt...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/boltwire.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
>
>
> *Join me January 1 for REVIVE :: 
> 2017http://www.fastmissions.com/boost/fast4god 
> *
>

-- 
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.

Re: BoltWire 5.11

[Dan Vis]

Yes, we have a problem with BoltWire not running on php 5.5 and up. Do you
know what version you have. We know what the issue is just haven't quite
fixed it yet.

Cheers
Dan

On Mon, Aug 21, 2017 at 2:59 AM, John Morris  wrote:

> Hi Dan,
>
> I too seem to be getting that pesky 500 internal server error, are you
> still offering help on this? Thanks sir
>>
>> John
>
> --
> 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.
>



-- 


*Join me January 1 for REVIVE ::
2017http://www.fastmissions.com/boost/fast4god
*

-- 
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.

Re: BoltWire 5.11

[John Morris]

Hi Dan, 

I too seem to be getting that pesky 500 internal server error, are you 
still offering help on this? Thanks sir
>
> John

-- 
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.

Re: BoltWire 5.11

[The Editor]

I'm not sure we are fully up to date for 5.6 yet. But we are getting
closer. And I agree, we just need to do it, and sooner rather than later.

I also need to set aside some dedicated time to work on this...

Cheers,
Dan

On Wed, Aug 10, 2016 at 11:15 AM Kevin Reed  wrote:

> Dan,
>
> Not sure I see it as problematic at all since everything before 5.6 is now
> end of life and not supported.  Current version of PHP is 5.6 and was
> released almost 2 years ago.
>
> 5.3, 5.4 and 5.5 are no longer supported and considered end of life.
> Security support for these versions has ended as well.
>
> http://php.net/supported-versions.php
>
> I have not had any time to look at the newer versions of BW for sometime,
> just don't have the spare cycles.  I am trying to block some time to start
> looking at it soon.
>
>
>
> --
> Kevin Reed
> TNET Services Inc.
>
> On Wed, Aug 10, 2016 at 8:35 AM, The Editor  wrote:
>
>> Yes, this is a bit problematic. We can't update to anything past php 5.5
>> without changing the preg_replace functions, and as soon as we update them
>> anything below php 5.2 gets invalidated. I think we are best to move
>> forward as the php changes are security related, and its something we need
>> to do eventually. We can put a note on the site that those with an old
>> version of  > php 5.3 must use the lower version of BoltWire. When we
>> transition to 6.00 (which should be fairly minor), we can officially drop
>> support for older versions of php.
>>
>> Open to other suggestions about how to proceed...
>>
>> Cheers,
>> Dan
>>
>> On Sat, Aug 6, 2016 at 5:59 AM mz  wrote:
>>
>>> Just checked that version 5.11 definately needs PHP 5.3 or later.
>>> PHP 5.2 does not support closures.
>>> You will likely see this error: Parse error: syntax error, unexpected
>>> T_FUNCTION
>>>
>>> Using PHP 5.3 this version 5.11 runs smoothly - at least for me for now.
>>>
>>> Greetings, Martin
>>>
>>> --
>>> 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.
>>>
>> --
>> 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.
>>
>
> --
> 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.
>

-- 
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.

Re: BoltWire 5.11

[Kevin Reed]

Dan,

Not sure I see it as problematic at all since everything before 5.6 is now
end of life and not supported.  Current version of PHP is 5.6 and was
released almost 2 years ago.

5.3, 5.4 and 5.5 are no longer supported and considered end of life.
Security support for these versions has ended as well.

http://php.net/supported-versions.php

I have not had any time to look at the newer versions of BW for sometime,
just don't have the spare cycles.  I am trying to block some time to start
looking at it soon.



-- 
Kevin Reed
TNET Services Inc.

On Wed, Aug 10, 2016 at 8:35 AM, The Editor  wrote:

> Yes, this is a bit problematic. We can't update to anything past php 5.5
> without changing the preg_replace functions, and as soon as we update them
> anything below php 5.2 gets invalidated. I think we are best to move
> forward as the php changes are security related, and its something we need
> to do eventually. We can put a note on the site that those with an old
> version of  > php 5.3 must use the lower version of BoltWire. When we
> transition to 6.00 (which should be fairly minor), we can officially drop
> support for older versions of php.
>
> Open to other suggestions about how to proceed...
>
> Cheers,
> Dan
>
> On Sat, Aug 6, 2016 at 5:59 AM mz  wrote:
>
>> Just checked that version 5.11 definately needs PHP 5.3 or later.
>> PHP 5.2 does not support closures.
>> You will likely see this error: Parse error: syntax error, unexpected
>> T_FUNCTION
>>
>> Using PHP 5.3 this version 5.11 runs smoothly - at least for me for now.
>>
>> Greetings, Martin
>>
>> --
>> 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.
>>
> --
> 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.
>

-- 
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.

Re: BoltWire 5.11

[The Editor]

Yes, this is a bit problematic. We can't update to anything past php 5.5
without changing the preg_replace functions, and as soon as we update them
anything below php 5.2 gets invalidated. I think we are best to move
forward as the php changes are security related, and its something we need
to do eventually. We can put a note on the site that those with an old
version of  > php 5.3 must use the lower version of BoltWire. When we
transition to 6.00 (which should be fairly minor), we can officially drop
support for older versions of php.

Open to other suggestions about how to proceed...

Cheers,
Dan

On Sat, Aug 6, 2016 at 5:59 AM mz  wrote:

> Just checked that version 5.11 definately needs PHP 5.3 or later.
> PHP 5.2 does not support closures.
> You will likely see this error: Parse error: syntax error, unexpected
> T_FUNCTION
>
> Using PHP 5.3 this version 5.11 runs smoothly - at least for me for now.
>
> Greetings, Martin
>
> --
> 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.
>

-- 
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.

Re: BoltWire 5.11

[mz]

Just checked that version 5.11 definately needs PHP 5.3 or later.
PHP 5.2 does not support closures.
You will likely see this error: Parse error: syntax error, unexpected 
T_FUNCTION

Using PHP 5.3 this version 5.11 runs smoothly - at least for me for now. 

Greetings, Martin

-- 
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.

Re: BoltWire 5.11

[TMurNGon]

Thanks for the update Dan.

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  
> 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 .
>> To post to this group, send email to bolt...@googlegroups.com 
>> .
>> 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.

Re: BoltWire 5.11

[The Editor]

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  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+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.
>

-- 
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.

Re: BoltWire 5.11

[TMurNGon]

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+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.

Re: BoltWire 5.11

[The Editor]

I just tried the ftp access and can't seem to get in. You should reset this
anyway, and send the new info to me directly, rather than posting to an
open list like this. :)

My email is fast4...@gmail.com. Eager to see if I can figure out what is
going on. Was out all day, but have a little time the next hour or so.

Cheers,
Dan

On Fri, May 27, 2016 at 1:03 PM erik burggraaf 
wrote:

> Hi Dan,
>
> FTP access is as follows.
>
> ftp.erik-burggraaf.com
> port 21
> username boltwire
> password acCesS42
>
> Thanks for looking.
>
> On May 27, 2016, at 10:31 AM, The Editor  wrote:
>
> Hi Erik,
>
> I had a feeling it was something else just because there weren't any error
> logs. In fact, I think the feature that was deprecated should have only
> generated a warning. To think it was completely changed to fatal error
> between 5.3 and 5.5 seems kind of abrupt for PHP, but I haven't researched
> it out.
>
> Anyway, I'm happy to help you get this going. If there's anyway you could
> send me temporary ftp access off list I'll be happy to take a look and get
> this debugged. I have not had anyone else mention problems, but you never
> know. I downloaded the script, installed it, and set up a test site on my
> server in literally 5 seconds. And everything worked perfectly. So I'm a
> bit puzzled and want to make sure it works on every server possible.
>
> My guess is your boltwire installation is not in the right place or
> something. It should look something like:
>
> / (root)
> /boltwire
> /boltwire/scripts/
> /boltwire/scripts/engine.php
> /field
> /field/index.php
> etc.
>
> And then index.php should include the following lines:
>
>  $BOLTadmin = 'admin';
> $boltwire = '../boltwire';  // must be a relative path
> include_once("$boltwire/scripts/engine.php");
>
> If you can't give me temp access to your server, I can give some debug
> suggestions but I can probably find and fix it faster that it would take to
> explain all that. :)
>
> Thanks for your patience and for giving us a try. If we can get you past
> this initial hiccup, I think you'll like the software.
>
> Cheers,
> Dan
>
> PS. Another possible issue is that there's some new function in 5.5.30
> that conflicts with BoltWire namespace. Probably lots of possibilities. No
> point speculating without more information.
>
>
>
> On Fri, May 27, 2016 at 11:32 AM erik burggraaf 
> wrote:
>
>> Hi Dan,
>>
>> Happy b-day and thanks for the upgrade.  It didn't fix the issue I'm
>> having with 500 internal server errors in my instalation.
>>
>> Thanks,
>>
>> Erik
>>
>> On May 26, 2016, at 3:00 PM, The Editor  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 

Re: BoltWire 5.11

[erik burggraaf]

Hi Dan,

FTP access is as follows.

ftp.erik-burggraaf.com 
port 21
username boltwire
password acCesS42

Thanks for looking.

> On May 27, 2016, at 10:31 AM, The Editor  wrote:
> 
> Hi Erik,
> 
> I had a feeling it was something else just because there weren't any error 
> logs. In fact, I think the feature that was deprecated should have only 
> generated a warning. To think it was completely changed to fatal error 
> between 5.3 and 5.5 seems kind of abrupt for PHP, but I haven't researched it 
> out.
> 
> Anyway, I'm happy to help you get this going. If there's anyway you could 
> send me temporary ftp access off list I'll be happy to take a look and get 
> this debugged. I have not had anyone else mention problems, but you never 
> know. I downloaded the script, installed it, and set up a test site on my 
> server in literally 5 seconds. And everything worked perfectly. So I'm a bit 
> puzzled and want to make sure it works on every server possible. 
> 
> My guess is your boltwire installation is not in the right place or 
> something. It should look something like:
> 
> / (root)
> /boltwire
> /boltwire/scripts/
> /boltwire/scripts/engine.php
> /field
> /field/index.php
> etc.
> 
> And then index.php should include the following lines:
> 
>  $BOLTadmin = 'admin';
> $boltwire = '../boltwire';  // must be a relative path
> include_once("$boltwire/scripts/engine.php");
> 
> If you can't give me temp access to your server, I can give some debug 
> suggestions but I can probably find and fix it faster that it would take to 
> explain all that. :)
> 
> Thanks for your patience and for giving us a try. If we can get you past this 
> initial hiccup, I think you'll like the software.
> 
> Cheers,
> Dan
> 
> PS. Another possible issue is that there's some new function in 5.5.30 that 
> conflicts with BoltWire namespace. Probably lots of possibilities. No point 
> speculating without more information.
> 
> 
> 
> On Fri, May 27, 2016 at 11:32 AM erik burggraaf  > wrote:
> Hi Dan,
> 
> Happy b-day and thanks for the upgrade.  It didn't fix the issue I'm having 
> with 500 internal server errors in my instalation.  
> 
> Thanks,
> 
> Erik
> 
>> On May 26, 2016, at 3:00 PM, The Editor > > 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+unsubscr...@googlegroups.com 
>> 

Re: BoltWire 5.11

[erik burggraaf]

Hi Dan,

Happy b-day and thanks for the upgrade.  It didn't fix the issue I'm having 
with 500 internal server errors in my instalation.  

Thanks,

Erik
> On May 26, 2016, at 3:00 PM, The Editor  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+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 
> .

-- 
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.