phylogram

Hi Jess,

thanks for your informative reply.

Update: After uninstall and reinstall I am not able to reproduce the issue. Sorry to bother you. Below is what was originally my post for reference.

The Action Scheduler version is 3.1.6. Which is according to packagist the newest version.

But I guess I actually found the issue in the newest version. I told them what I found: https://github.com/woocommerce/action-scheduler/issues/558#issuecomment-635277860

• This reply was modified 4 years, 6 months ago by phylogram.

Thank You – I guess I have to delay that, but I will certainly do that.

I am not used to debug autogenerated code. How would I do that. My guess in this case:

I check with code does interact with the element affected, exclude one by one in autoptimize as trial and error. If am no lucky I go on and see, if there is javascript that interacts directly with css.

Is this quite right?

The second did it (without and with the first). Tanks – that was fast and helpful!

Thank You for your reply. I checked something like “that’s not a support question”. I hope, that I did not cause any inconvenience.

Hi @ninjateam, hi Tommy,

thank you for your reply. Unfortunately this was an expression of opinion, not a support question. I am sorry, if this seems rude, but I thought if you are going to sell premium / pro plugins, you might want to be informed.

If I use your plugin for a client – and this will mean PRO is unavoidable – I need it to be trustable. I do not have time to check the whole thing for security wholes. Basic SQL-errors give me an headache (this is even just MySQL). This may be neurotic, sorry, but wordpress allows badly written plugins.

To answer your questions:

1. No, this has not been not the currently latest version (2.3). I had installed it before the upgrade. However, this seems like an error, you should find and fix before publication, so I went for a different solution.
2. PHP-error-messages seem to be quite sufficient to understand the cause of the error. I have not reviewed the code however. So I am not going to install the plugin you recommended, because I can read php-error-logs.

I appreciate, that you put the effort into providing the free part of your plugin. However, for providing professional services, I need a certain standard of coding. Debug.log should not be filled with hundreds of error messages for a every-day-task / the main functionality of a plugin.

Thank you for your time and effort. I hope your last update did solve the problems. By the way, sorry for my English – I am not a native.

Philip from @phylogram

• This reply was modified 5 years, 4 months ago by phylogram.
• This reply was modified 5 years, 4 months ago by phylogram.