|
Richard Duncan
|
April 24, 2015 at 2:06 pm
Hello,
I copied template files into the upload directory as indicated in the instructions so that we can customize them.
I noticed that these files have numbers after .php
Am I supposed to leave those numerical suffixes in place?
When I did, the changes to the files had no effect on the site.
When I deleted the numerical suffixes, then chages to the files affected the site exactly as anticipated.
However, the next day, the files have been overwritten with the numerical suffixes again.
What is going on that I am missing here?
|
|
Lorenzo Orlando Caum
|
April 24, 2015 at 2:41 pm
Hi Richard, they are not suppose to have numbers as that would cause them to stop working since Event Espresso would no longer see the files that it is looking for.
Are you using a virus scan or a security plugin / service?
—
Lorenzo
|
|
Richard Duncan
|
April 24, 2015 at 3:04 pm
That is what I assumed.
It must be some security process that Page.ly is running that makes the changes.
I’ll pass this issue off to Page.ly if you are telling me that this is not being caused by configuration problem on my end that causes Event Espress to change the file names as described.
|
|
Lorenzo Orlando Caum
|
April 25, 2015 at 11:42 am
Hi, I think it would help to get in contact with them about this as this isn’t the expected behavior.
If your template name was say event_list.php and its being changed to event_list-123.php, then that will cause your customizations to be deactivated since Event Espresso is looking for event_list.php.
Hope that makes sense! Do let us know what you find out.
—
Lorenzo
|
|
Richard Duncan
|
April 25, 2015 at 1:43 pm
Pagely reported that their security daemon disables php code files in the uploads directory (by adding numbers to the file names) because that is a common location for exploits and hacks to occur.
To resolve the issue, they implemented a special configuration to allow Event Espresso files to live in the uploads directory and be ignored by the security daemon.
|
|
Lorenzo Orlando Caum
|
April 25, 2015 at 1:57 pm
Thanks for sharing how you solved the issue Richard.
So if another member using Event Espresso runs into this issue, just ask them to open a support ticket with Pagely regarding their security daemon?
As a sidenote, could you tell us about your experience with Pagely in terms of performance and support?
Did you need to setup caching exclusion rules for your Event Espresso pages?
I see that is it a managed WP hosting platform similar to Flywheel and WP Engine so I imagine your website must be pretty fast!
—
Lorenzo
|
|
Richard Duncan
|
April 25, 2015 at 2:19 pm
Yes, if another Event Espresso user encounters the issue they need to open a support ticket with Page.ly
Out site is still in development, so we have not yet finished configuring all the features, but I will report back as we do so.
|
|
Dean
|
April 27, 2015 at 1:00 am
Thanks again Richard, that information could be really helpful to any other Page.ly users.
|
