leeppolis
Forum Replies Created
-
Forum: Plugins
In reply to: [Intuitive Custom Post Order] Problems after removing the pluginFound the problem:
the additional
term_ordercolumn added to thewp_termstable is correctly removed when the plugin gets removed, but in my installation that same column was used by another plugin and this caused the problem.S.
Forum: Plugins
In reply to: [Simply Static - The Static Site Generator] Possible to run on a schedule?Have you been able to make it work?
Calling wp_remote_post() on that URL returns -1 to me.
Any advice?Forum: Fixing WordPress
In reply to: MySql Error log flooded with errors from WordPressYes, you’re right, sorry for my answer.
So, deactivating Jetpack it stopped logging warnings…
Replacing my custom theme with twenty sixteen, the log started being flooded again, but with different warning messages (these are just a sample)2017-02-15 14:24:42 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO
so_options(option_name,option_value,autoload) VALUES (‘theme_mods_twentysixteen’, ‘a:1:{i:0;b:0;}’, ‘yes’) ON DUPLICATE KEY UPDATEoption_name= VALUES(option_name),option_value= VALUES(option_value),autoload= VALUES(autoload)
2017-02-15 14:25:04 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTOso_options(option_name,option_value,autoload) VALUES (‘_transient_is_multi_author’, ‘1’, ‘yes’) ON DUPLICATE KEY UPDATEoption_name= VALUES(option_name),option_value= VALUES(option_value),autoload= VALUES(autoload)
2017-02-15 14:25:04 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTOso_options(option_name,option_value,autoload) VALUES (‘_transient_twentysixteen_categories’, ‘2’, ‘yes’) ON DUPLICATE KEY UPDATEoption_name= VALUES(option_name),option_value= VALUES(option_value),autoload= VALUES(autoload)Forum: Fixing WordPress
In reply to: MySql Error log flooded with errors from WordPressYou’re right, sorry for the reply.
So, deactivating Jetpack the logging stopped.
Activating the twetysixteen theme instead of my default theme, a lot of new warnings started being logged:2017-02-15 14:25:06 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO topics (keyword, query, volume) VALUES (‘#VenezuelaConTareck’, ‘%23VenezuelaConTareck’, ‘0’) ON DUPLICATE KEY UPDATE volume = ‘0’
2017-02-15 14:25:06 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO topics (keyword, query, volume) VALUES (‘#IBMGoT’, ‘%23IBMGoT’, ‘0’) ON DUPLICATE KEY UPDATE volume = ‘0’
2017-02-15 14:25:06 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO topics (keyword, query, volume) VALUES (‘#FelizMiercoles’, ‘%23FelizMiercoles’, ‘0’) ON DUPLICATE KEY UPDATE volume = ‘0’
2017-02-15 14:25:06 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO topics (keyword, query, volume) VALUES (‘#bfc530’, ‘%23bfc530’, ‘0’) ON DUPLICATE KEY UPDATE volume = ‘0’
2017-02-15 14:25:06 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO topics (keyword, query, volume) VALUES (‘#AtlantaAlive’, ‘%23AtlantaAlive’, ‘0’) ON DUPLICATE KEY UPDATE volume = ‘0’
2017-02-15 14:25:06 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO topics (keyword, query, volume) VALUES (‘#SecDef’, ‘%23SecDef’, ‘0’) ON DUPLICATE KEY UPDATE volume = ‘0’
2017-02-15 14:25:06 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO topics (keyword, query, volume) VALUES (‘#njmorningshow’, ‘%23njmorningshow’, ‘0’) ON DUPLICATE KEY UPDATE volume = ‘0’
2017-02-15 14:25:06 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO topics (keyword, query, volume) VALUES (‘#FoxKatZ1035’, ‘%23FoxKatZ1035’, ‘0’) ON DUPLICATE KEY UPDATE volume = ‘0’
2017-02-15 14:25:06 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO topics (keyword, query, volume) VALUES (‘#BlownOff’, ‘%23BlownOff’, ‘0’) ON DUPLICATE KEY UPDATE volume = ‘0’
2017-02-15 14:25:06 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO topics (keyword, query, volume) VALUES (‘#Malden’, ‘%23Malden’, ‘0’) ON DUPLICATE KEY UPDATE volume = ‘0’
2017-02-15 14:25:06 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO topics (keyword, query, volume) VALUES (‘#POWERGetUpCrew’, ‘%23POWERGetUpCrew’, ‘0’) ON DUPLICATE KEY UPDATE volume = ‘0’
2017-02-15 14:25:06 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO topics (keyword, query, volume) VALUES (‘#FOX13GMM’, ‘%23FOX13GMM’, ‘0’) ON DUPLICATE KEY UPDATE volume = ‘0’
2017-02-15 14:25:06 1358 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO topics (keyword, query, volume) VALUES (‘#BurnASongOrBand’, ‘%23BurnASongOrBand’, ‘0’) ON DUPLICATE KEY UPDATE volume = ‘0’(This are just few of them)
Forum: Fixing WordPress
In reply to: MySql Error log flooded with errors from WordPressYeah, thanks, this means that Jetpack (an official plugin coded by Auttomatic) is bugged?
That doesn’t really make sense to me. Either it looks impossible that no one noticed the problem before me…Forum: Fixing WordPress
In reply to: Automatic updatesHi,
I don’t remember this last update, I have 4.1 now, but it is happening since 2 or 3 updates, and on every WP installation I have on the same server.
I suppose it is a matter of server configuration, but since the http process is running as the same user that owns the directories (using The Apache 2 ITK MPM) I really cannot understand where the problem is.
Thanks,
S.I’ll do it now, thanks.
And then I’ll make a donation.
S.Here is an example of wrong tweet generated by the plugin.
It used to work before the latest 2 upgrades:– http://news./rasheed-chappell-break-loose/?utm_campaign=&utm_medium=twitter&utm_source=twitter – #Big-Daddy-Kane #DJ-Scratch #Kenny-Dop