I've seen people on the forum suffering if they do something in PHP that causes Actinic to crash. This is quite common in PHP but is usually fine in most development tools as you can just close the program in windows task manager and then edit it before running the code again.
The problem in Actinic is that the PHP will autorun for the previews and therefor crash or hang before you get a chance to edit it.
Can I suggest that Actinic looks into some way of disabling PHP on start up so people can get back into Actinic and edit the offending code?
Possible solutions that come to mind include:
- A command line option to disable php on start up?
- Or the same thing to disable previews (would this stop the php)?
- Or maybe a php.ini option somewhere that could be easily edited to turn off the php.
Mike
The problem in Actinic is that the PHP will autorun for the previews and therefor crash or hang before you get a chance to edit it.
Can I suggest that Actinic looks into some way of disabling PHP on start up so people can get back into Actinic and edit the offending code?
Possible solutions that come to mind include:
- A command line option to disable php on start up?
- Or the same thing to disable previews (would this stop the php)?
- Or maybe a php.ini option somewhere that could be easily edited to turn off the php.
Mike
Comment