LMEls

@roaftech As expected then – was wondering if it was a weirder thing than it already is ??

I hope they’ll fix it soon, because it’s really very annoying. The prompt is super useful in day-to-day editing, but if it’s always there, it becomes useless, and I always have to second guess myself: “did I already click the update button? Did the change go through? Better click it again to be sure, since the prompt could be right this time…”

@roaftech Would the previously created sites not start exhibiting the problem if you updated WordPress in those sites?

Same story here. Brand new install, no WooCommerce, just the Classic Editor plugin.
On all up-to-date sites I’m working in the last couple of weeks.

Right – didn’t realise the dependency installer was a separate thing from your plugin.

Thanks for the plugin itself btw, it’s much needed!

Yes, that’s true. I’m ashamed too, as I was under the impression I had updated that server to use 7.2 already, and it’s now very clear that’s not the case.

It does explain why I didn’t encounter any problems with this plugin on other sites ??

I don’t expect you to support PHP 5.2. (although the constant not being in quotes might be worth fixing, as I think PHP 7.2 is still picky about that as well)

Hi Pieter,

I get the same problem, and since I just now installed it, I think I would have used the updated version? It says version 2.3.1, and installing works, but it refuses to activate with the error message below.

In case it’s important, this is on two sites that have not yet been updated to WP 5, they’re at WP 4.9.9.

It gives me 1 notice, 2 warnings, and 1 fatal error.
(replaced our own server path with […])

Notice: Use of undefined constant __DIR__ – assumed ‘__DIR__’ in /[…]/wp-content/plugins/classic-editor-addon/classic-editor-addon.php on line 29

Warning: include_once(__DIR__/vendor/autoload.php) [function.include-once]: failed to open stream: No such file or directory in /[…]/wp-content/plugins/classic-editor-addon/classic-editor-addon.php on line 29

Warning: include_once() [function.include]: Failed opening ‘__DIR__/vendor/autoload.php’ for inclusion (include_path=’.:/opt/plesk/php/5.2/share/pear’) in /[…]/wp-content/plugins/classic-editor-addon/classic-editor-addon.php on line 29

Fatal error: Class ‘WP_Dependency_Installer’ not found in /[…]/wp-content/plugins/classic-editor-addon/classic-editor-addon.php on line 30

Hope this helps, but let me know if I can provide more info!

—
Els

I’m indeed running latest versions of both WP and the TWPro.
I’ve disabled both other plugins (capability manager and download monitor), and waited until the hour was over, and API limit was reset.
The tweets came back.
Then enabled the plugins, one by one, but now the tweets are still on the page, while the limit was reached. I did not change anything else at all.

Do you know of anything else that could have caused the tweets to stop appearing on the page? Or is ‘deactivate’ and ‘activate’ on the other plugins enough of a fix by itself?

Hi Aaron,

I just installed the plugin on two separate sites (also separate hosts, and separate twitter accounts), and noticed that:

on one site I get a 150 limit
on the other a 20000 limit

Both sites however, use more API calls than 1 per 5 minutes.
With the result that the 150 limit one, finishes this limit in under half an hour. In fact, just now the limit should have been reset, but 8 minutes into it, with a non-busy website, 150 have been used again.
Or maybe still? Is it possible something else is wrong so that it just keeps hanging at 150 used?

The main problem though, is that no tweets appear on the page in this situation. I don’t see any cached tweets.

Is there anything to be done that makes sure the latest set of tweets remains on the site until the limit is reset? Currently, I get white space once the 150 are gone.