|
thomaspointbeach
|
December 21, 2016 at 10:16 am
From my understanding, there should be as many Message Types in Default Messages as there are active Message Types under Email Settings. This is not the case for me. I only have 2 Message Types under Default Messages.
I am going to go out on a limb here and guess (taking the other Email issues that have shown up) that the Ticket Add-On, or something, is not correctly activating (cron tasks and adding Messages…). I am going to test by disabling and re-enabling the Ticket Addon…
WELL NOW… THAT CERTAINLY STINKS…
Deactivating and reactivating the Ticket Add-On seemed to CLEAR ALL OF MY MESSAGES…
Fantastic!
|
|
thomaspointbeach
|
December 21, 2016 at 10:21 am
Oh man… That is SUPER NEAT. ALL of my message templates are gone. GONE. All of them, custom ones too! I just lost quite a bit of time, and, expecting to have my settings saved (or, at least, not being notified they would go away in any appreciable manner) I now have to take my site offline. Because, in addition to losing all of my messages, they did NOT come back when I re-activated the plugin, not even the DEFAULT ones…
WHAT?
|
|
thomaspointbeach
|
December 21, 2016 at 10:27 am
Ok… new issue. I thought it may be because I had requested a key reset, and haddn’t re-upped the key in the system, so I un-set my key, saved, set my key, saved, and got a green key again.
But now I am getting all sorts of errors: The [ESPRESSO_CALENDAR] shortcode has not been properly registered or the corresponding addon/module is not active for some .... Well, it is active… So… How bad is my whole site buggered now? Hmm…
|
|
thomaspointbeach
|
December 21, 2016 at 10:29 am
Scratch that, somehow it got deactivated. That was weird.. Still, no messages… And that is ver-bad…
|
|
Josh
|
December 21, 2016 at 10:33 am
Hi there,
I’m not sure what you’ve been doing that led to the messages getting removed, but are you certain that the different message types are set to be active on the Event Espresso > Messages > Settings page?
|
|
thomaspointbeach
|
December 21, 2016 at 10:35 am
UPDATE:
– Deactivating Ticket Add-On deactivates the message types.
– Un-Activated Message Types do not show up in Default or Custom.
– Re-Activating Ticket Add-On does not reactivate the message types.
– Manually re-activating the message types does bring back the Default template and any related Custom templates.
– Just because a Type is “Active” does not mean that it have a Default.
– If a default is missing, de-activating the message type and re-activating it will create the Default Template.
This is resolved (for me) but it seems there is a bug in here somewhere. As I had all of the types activated (or, they were activated by a plugin or install or something) and yet only had (prior to buggering the whole thing up) the Ticket and Ticket Notice types in Default.
I am now all set…
|
|
thomaspointbeach
|
December 21, 2016 at 10:36 am
I can confirm that all types “were” active, but only had 2 Defaults listed (prior to de/re-activation issue).
|
|
Josh
|
December 21, 2016 at 10:43 am
I checked on a few test sites and I’m not able to reproduce the issue where deactivating the Ticketing Add-On deactivates any of the non-ticket message types. The *only* message types that should be deactivated would be message types that the Ticketing add-on adds, like the Ticket Notice message type.
|
|
thomaspointbeach
|
December 21, 2016 at 11:07 am
Yes, that is what I meant. De-activating this add-on de-activates Ticket and Ticket Notice, but re-activating it does not re-activate those types (confirm?).
As for the other types. They were activated in Email Settings, but their default templates were not added/populated.
You may need to test with a fresh install (fresh WP, and add the plugins).
Also, it should be noted that I installed my plugins with WP Cli as well. I activated via the Web Interface, however, so that should not be an issue. Installation should only move the files in to place, then the activation of the plugin should trigger the appropriate set-up. So I do not think that is part of the issue, and if it is, it wouldn’t make sense, because that would also mean that un-zipping the files in to place would also cause the issue…
|
|
Josh
|
December 21, 2016 at 11:13 am
It seems from some of the issues you’ve posted that you may have been experimenting with customizations of the Event Espresso codebase. Is it possible that some of the experimentation you’ve been doing is leading to this odd behavior? Default templates should be populated after the initial plugin activation. Those templates, as well as custom templates should not get wiped out later on.
|
|
thomaspointbeach
|
December 21, 2016 at 11:22 am
Very fair assumption.
I have seen weirder things, so, yes, it is a possibility. That said, I have been primarily modifying display code, and I don’t believe anything I have modified to date persists any data, or modifies any run-time data. The biggest thing *may* be a 500 error that causes a routine to fail before finishing, but even so, those hooks occur on update, and I only did that once, and only when the code was stable.
So, I don’t know. But, again like I said, I have see weirder, so it is possible.
Unfortunately I don’t believe I can test without a fresh install, which I neither have time for, nor a key for. So I will wait on that. I will be sure to test it though when/if I get a chance.
|
