|
Erica Lange
|
December 11, 2015 at 1:16 pm
We had a developer produce a special shortcode so our attendee list would include info not displayed with the [ESPRESSO_EVENT_ATTENDEES]. I updated to the 4.8.26 it has been removed. Do i need to restore my site to find it, copy it and then add it again?
WordPress Version:
4.3
PHP Version:
5.4.28
MySQL Version:
5.5.46
Event Espresso Version:
4.8.26.p
WordPress Address (URL):
http://www.azbuilders.org
|
|
Josh
|
December 11, 2015 at 1:35 pm
If they added the custom code directly to core, and then you add it back to core, you’ll lose it again on the next update. You can avoid losing the changes by adding the shortcode in its own plugin, which the developer should have done initially.
|
|
Erica Lange
|
December 17, 2015 at 12:18 pm
Thank you. We went back to our IT and they corrected it. their explnation of what happen was as follows:
“When the Events Espresso Plugin was updated – one of the event details actions was no longer working – keeping it from correctly pulling in the short code information. The total time to research and correct the issue was 2 hours.” for which they are billing us. Thoughts on this?
”
|
|
Lorenzo Orlando Caum
|
December 17, 2015 at 2:03 pm
Hi Dana,
The information that Josh shared is still valid. If the shortcode information was added directly to the core plugin, then those changes would be lost when you updated.
This is because the core plugin is removed and replaced during a software update. This is a similar process to other WordPress plugins.
Could you ask your developer how the shortcode was extended to add the additional options?
—
Lorenzo
|
|
Erica Lange
|
December 22, 2015 at 10:36 am
Thank you. Our IT insists they installed it outside. Will be an separate file or document in the folder?
Also when you ask about asking how the shortcode was extended….are you asking because it would help trouble shout my issue, or you can’t figure how to replicate it. I don’t think it’s the latter, but wanted to answer your question clearly.
|
|
Josh
|
December 22, 2015 at 11:10 am
It sounds like they had to update their code to make it compatible with the newer version because of a change that was included in an update. We try to not break backwards compatibility, but they may have used a hook that we didn’t intend to be used the way they used it. I’m glad they were able to resolve this for you.
We do not need to know how the shortcode was extended.
|
