jondaley

wp_using_ext_object_cache() is true.
wp_cache_get(static::ACTIVATION_TRANSIENT)
returns false very often.

That is at least part of the problem.

• This reply was modified 1 year, 7 months ago by jondaley.

I’m curious about the ordering of line ~90 in Activation.php, where you set the transient/cache value and then erase the other. I don’t know your code or W3’s code, but it seems safer to erase and then create?

UPDATE: I swapped the order and it doesn’t make any difference to the “random” last_run_time false vs a timestamp.

• This reply was modified 1 year, 7 months ago by jondaley.

Definitely it happens more than once a day – I’ve seen multiple simultaneous operations – perhaps the logic is bad in not setting that it is working until the operation is completed, so if simultaneous users come in, it will run a bunch of times before the first one completes?
This site has a higher-than-average number of users who have logins. (10,000 users, though a lot of those are old; probably 500 are actively using the site on a regular basis)

if(update) check has passed and run the schema_builder->up() 44,000 times since I last wrote to you.

I am using W3 total cache. I assume these settings are the defaults, but these seem relevant:

Default lifetime of cache objects:?1800 seconds
Garbage collection interval:?3600 seconds
Store transients in database: No

| 72659615 | tec_ct1_series_relationship_table_schema_version | 1.0.0 | yes |
| 72659616 | tec_ct1_events_table_schema_version | 1.0.1 | yes |
| 72659617 | tec_ct1_occurrences_table_schema_version | 1.0.2 | yes |

Great, thanks. That looks likely.

I added a logging statement inside the if(update) block, and on a page load to the home page and it ran that code 7 times, 5 times via the user, and twice via cronjob.

I added a second statement inside the if(!fully_activated) and that code never runs.

Is it expected to have this code running that many times. I can see it running on each user’s visit to the site (it ran 80 times while typing this message)

I’m running 6.0.12.

I found it. My main site has more options configured for W3 total cache enabled. I’m not sure which setting is making the events plugin have problems.

Adding my /events/community/add page to the “never cache the following pages” setting makes them be able to work together.

Your description of the fix doesn’t sound like my problem, so perhaps you are chasing multiple bugs currently?

I have the same behavior – where the image can’t be uploaded from the front end, but I am fine on the backend. (I didn’t test that I’m still fine with this version on the backend, but I have the same error as originally reported with the new version as well).

That sounds great, thank you!

When re-saving, if you mean re-uploading an image from the wp-admin page, yes, that works fine. If you mean just going to the event and re-uploading the image, yes, that works fine.

I downgraded to 6.0.1 and 6.0.1.1 and see the same thing.

created a ticket in your system.

Not getting a reply, I downgraded both. I can confirm downgrading to 6.0.2 for both the free and pro plugin does *not* fix the problem.

I got my customer’s login to your site. I can see the download for 6.0.2 for both plugins – do I want both, or just one? Also, it sounds like you opened a ticket on your side, or should I open one there too?

Great, thank you!

I included the filename and function calls in a previous comment.

I don’t think caching can be the problem, unless there is a javascript file that is being included without a version number appended to it, but I use a cache-busting plugin to append ?adsasdlkajsdljd to every static file, so even if you don’t include cache busting code on your side, it should do it on its own, and I’m modifying the php files and seeing the updates immediately, so nothing in PHP is being cached incorrectly.

In Submission_Handler.php: media_handle_upload() eventually calls wp_get_image_editor() and then wp_get_image_editor() is called on line 325 as well. I haven’t dug into your code enough to know if this all seems reasonable or not.

Do you expect load() to get called twice?

I’ve added some debugging statements to wp-image-editor-imagick->load(), and it is called twice, once with a proper image, and then a second time with an invalid file.