PHP Files

[IProto]

Hi there I'm using snippetmaster (2.1.1) to edit some files that have a little bit of php embedded into them and I'm having some problems.  I believe this was mentioned before in the beta forum but I might aswell post it again, plus mine does something slightly different.

When parsing the php in the file it will commonly change <php to <--p or something like that.  That was the problem that was previously posted.  Another problem I'm having is that some of the php is in quotations (I'm using it to pull an image, code will follow) and it's formatting characters like < to #lt;.

Here's the context:

Code:

background="/images/<?php echo($year.'/images/'.$month.'-1.gif'); ?>"

and that code gets changed to:

Code:

background="/images/&lt;?php echo($year.&#39;/images/&#39;.$month.&#39;-2.gif&#39;); ?&gt"

The client I'm doing this for is less than thrilled about this and is breathing down my neck to get this fixed.  Any help would be appriciated.

[admin]

This is a known problem, and is something I'm planning to have "fixed" for the next release. 

I'm hoping to make the next release by Friday evening, but I might delay over the weekend as I've run into a snag with something I'm working on... So might be later Sunday.. Monday at the latest.

Sorry for the delay!

[IProto]

Thanks for the quick reply.  I may actually get to keep my head after all then =)

[admin]

OK, I've been wrestling with this problem for a few days now... it is "partially" fixed, but I need to get this release out the door so I'm going to have to put this on hold for a bit.

When the new version is released, please be sure to test it out and let me know.  If php is included in a URL, it won't be properly "preserved", and this is something I wasn't able to fix right now.  I have a few ideas how to fix this, but I just ran out of time and need to get the new version out asap because there's a few other bugs/fixes that need to go out.

But... rest assured I will be working on this problem immediately after the new release is done.  I'll hopefully get this 100% fixed for the next release after this one.  (A few weeks...)