Finally, you probably also want to delete. However, if you want to reuse your codes, then copy the files first (frommartti wrote:Disable.MarieNatalie wrote:Could you please tell us... just disable or and DELETE data?martti wrote:This extension does not work on the phpBB 3.1.6 version, please disable extension BEFORE update to 3.1.6 version.
Thanks in advance
store/customcode)
That's true. But for small things it should not be a problem..martti wrote:It's always better to have a clean separation between the core and anything else, imho.Solidjeuh wrote:I noticed in phpbb update that auto update still is merging files
So would it not be easyer to just edit the code files like before?
Or am I mistaking?
I have followed all of your instructions and your alternative solutionmartti wrote:Finally, you probably also want to delete. However, if you want to reuse your codes, then copy the files first (frommartti wrote:Disable.MarieNatalie wrote:Could you please tell us... just disable or and DELETE data?martti wrote:This extension does not work on the phpBB 3.1.6 version, please disable extension BEFORE update to 3.1.6 version.
Thanks in advancestore/customcode)
hmmmm This escaped my attention.david63 wrote:That idea, whilst good, would not get past validation.KillBill. wrote:Idea change ext code:
1. you create new folder ext/marttiphpbb/customcode/styles/all/template/customcode
2. add info this folder change chmod 777
3. you change event/ all html include path
It is not allowed to add/delete/modify files within an extension. The way that it is handled at the moment is, as I understand it, the correct way. The issue is to resolve the Twig change (which may be a bug)
It won't be possible to get this extension to work with 3.1.6 due to path limitation of the template engine. Please see here for a workaround.John connor wrote:Well this suxx. I updated my local install in Xampp to make sure 3.1.6 worked before I went live and I'm sure glad I did because I had a blank screen and I seen that I needed to disable this ext's style to get into the ACP.
So with that I won't be updating my live site until this extension works with 3.1.6. I need this ext since i have custom code that plays audio and code in the footer!
I can't predict the course of phpBB. If it will be decided that extensions can add extra paths to the template engine then it will be possible to adapt this extension, otherwise not.John connor wrote:Will this path limitation be the same for future phpBB releases? Will you redesign this ext to work with this? Or are we stuck with the workaround?
I can't predict the course of phpBB. If it will be decided that extensions can add extra paths to the template engine then it will be possible to adapt this extension, otherwise not.John connor wrote:Will this path limitation be the same for future phpBB releases? Will you redesign this ext to work with this? Or are we stuck with the workaround?
Why does it fail?Raul [ThE KuKa] wrote:not works on 3.1.6 version
See posts above yours.AmigoJack wrote:Why does it fail?Raul [ThE KuKa] wrote:not works on 3.1.6 version
I don't know precisely if phpBB changed a configuration for Twig or that Twig got stricter itself. There was an update to a newer version of Twig. In a way it's better security to have the path restricted. But there's is no option for extensions to add template paths for I can see.AmigoJack wrote:That still doesn't precisely tell me why it worked on previous phpBB releases. Is it an issue to 3.1.6, or is it an issue with Twig?
