Paul

Thank you for your answer.

I tried the first option with no luck. Can you give me more details please?

When i go to All posts in back-end i get this:

Fatal error: Call to a member function setTimezone() on a non-object in /home/xxxxx/public_html/wp-content/plugins/content-scheduler/includes/DateUtilities.php on line 16

PHP version: 5.3.26
Content Sceduler version: 2.0.3

There are already woocommerce functions about stock visibility that act the same way. Is possible to hook in these actions and hide the products (instead of stock_status) based on my custom field?

I make a fresh install in a test environment and i think there it works fine.

I also use a CDN. Could be that a problem? Thank you.

After update i get these erros when someone left a comment. Also in the log entry i get double entries for one comment even when i set the limit to 1 per post. For now i get back to 1.2.3 version.

Parse error: syntax error, unexpected T_STRING in /home/database/public_html/wp-content/plugins/mycred/addons/notifications/myCRED-addon-notifications.php(153) : runtime-created function on line 1

Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /home/database/public_html/wp-includes/plugin.php on line 173

Warning: Invalid argument supplied for foreach() in /home/database/public_html/wp-content/plugins/mycred/addons/notifications/myCRED-addon-notifications.php on line 74

Awesome work Gabriel! I am looking forward for the Newsletter plugin support! Thank you!

Awesome! Thank you Aaron

In New post > Post Expirator inside Expiration Categories:

I send it in your personal email address.

Thank you…

I use this theme https://themes.mysitemyway.com/modular/ but is a premium theme.

Is it possible to send you the theme?

Thank you…

I tested it and it works!

Thank you Marco!

I did that but i get the same blank page…

@marco

Thank you for your answer but didn’t work…

Yes it seems that is a bug. Thank you for your answer @mightypixel.

I tried this but didn’t work for me…

UPDATE:

I tested in some different environments and all works fine if i have a few users.

When i have a lot of users (10.000+) something goes wrong and i get a blank screen even with memory_limit set to 256M or higher