matiyin

Similar here. I just installed the latest plugin first time on WP6.1.1. When I try to Create a feed, WP crashes with a critical error which looks like memory exhaustion while having a 512Mb memory_limit on the server.

Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /data/sites/wp-includes/functions.php on line 7022


Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /wp-includes/functions.php on line 2162


Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes) in /data/sites/wp-includes/meta.php on line 1189

There has been a critical error on this website. Please check your site admin email inbox for instructions.

Learn more about troubleshooting WordPress.

I created the folder structure in /uploads/woo-product-feed-pro myself, as I saw in Settings they were not existing and writable, which they are all now. Not sure if related, but confusing.

Hi Mat,

thanks for following up. I didnt manage to make the WP plugin run archiving again, even though I tried with plugins deactivated and none of my plugins are in your mentioned list. Strangely enough, it ran fine for a while until I got a mssg from my client that reports could not be generated anymore.

Meanwhile I’ve switched to on premise on the same server, which is running smooth until now. I didn’t have time/budget to dive deeper into the issue on WP.

Thanks,

matiyin

Hi mat,

i understand it’s not easy to reproduce. I’ve disabled all plugins and even switched to the default WP 2022 template, but the same error persists.

—
PHP Fatal error: Declaration of Piwik\\Container\\IniConfigDefinitionSource::getDefinition($name) must be compatible with DI\\Definition\\Source\\DefinitionSource::getDefinition(string $name) in $abs_path/wp-content/plugins/matomo/app/core/Container/IniConfigDefinitionSource.php on line 23
—

Everything worked fine until I upgraded to 4.6. I don’t know what the error implies, but maybe my tracking data in the db is corrupt or somehow incompatible. I could erase everything and reinstall, maybe it will help but sceptic now about using this plugin. It’s not been reliable from the start and my client is getting impatient and want to switch back to google. All tracking data from the last months is useless, since we cannot generate a report.

Too bad, I might try on premise in my own free time.

thanks, I can confirm it works again in v1.0.9.20

please pull again. I experienced issues as well on an SSL enabled site. Turned out there where a few more places with pointing to http. Should be better now.

https://github.com/matiyin/acf-google-font-selector-field

• This reply was modified 6 years, 1 month ago by matiyin.

Hi Damian,

I’m using it in a production environment and have no issues. Without any demo environment, screenshots and any console errors you might see I don’t know how I can help you further.

It’s working fine here. Can you be more specific as to what ‘stopped’ working exactly?

I’ve made a fork with the changes (explained in top of readme): https://github.com/matiyin/acf-google-font-selector-field

how?

Hi Chris,

I just used the plugin in a project and found that the preview indeed didn’t work in the current version. I’ve fixed it in the ACF5 version of the plugin and added some additional stuff I needed.
If you want I can send you my code version so you can see the changes I made, or point you in the right direction to make fixes yourself.
Let me know if you still need it.

Grtz,

Martijn

I encountered the same issue with the latest Polylang 1.8.3 and WP 4.4.2.

https://www.domain.com/en would give a 404 whatever settings I used. I digged in and found that renaming or disabling the custom taxonomy I use would make it work.
Then I enable this custom taxonomy again and it continues to work unless the permalink rewrites are flushed.

So there seems to be an issue related to custom taxonomies and permalink rewrites in Polylang.

So if you have the same problem, and are using a theme with custom post type and custom taxonomies, check out this work around:
– temporarily rename or comment out the custom taxonomy in your theme’s functions.php
– check if it now works
– set back the changes you made, and be sure not to flush permalinks.

Same here, the plugin v2.4.6 is currently broken on WP 4.4.2. It doesn’t show any image to crop in the interface. It worked for over a year on the same site, so something in the WP Core update messed with the plugin.

Hi,

I’ve just solved an issue similar to yours.

I had a big repeater inside a repeater and when the client was filling it we came to a point where we couldn’t save the page anymore. The server would hang on a resource time out, it would try to save for a few minutes and then the server gave an error.
I tried many things but found out just now that when I turn off Post Revisions that saving works fine!

Set this in your wp-config.php:

define(‘WP_POST_REVISIONS’, false);

Maybe it helps in your case too.

To the developer: I’ve found an issue where a big repeater in repeater will hang the server due to not enough resources on save. This is because Post Revisions were enabled. Without revisions saving became possible again, because it’s 10 times faster.

Excellent news!

I think I managed with some workaround for the particular project.

I’m waiting for a while now for 3.2 that promises more crucial bug fixes.

Cheers and thank you for your time and effort.

Found out that this is a compatibility issue with WPML.
Will make a new thread.