chrisbfinternet

Agree with Vassilis on this one, I was just about to post the same.

Quick editing a non-public post (changing just the title, for example) turns the post type to “Post”. There is no way to retain the original post type, because it is not listed in the dropdown as an option.

Hi there,

We had another one today. It started life with an old version of the plugin, but was maintained with upgrades.

The fix outlined above did the trick (and has worked 100% since) but here is the contents of the wp_wsal_options table prior to deleting:

(1, 'wsal-pruning-date', '1 month'),
(2, 'wsal-pruning-limit-e', ''),
(3, 'wsal-pruning-limit', '5000'),
(4, 'wsal-promo-send-id', '1'),
(5, 'wsal-pruning-date-e', '1'),
(6, 'wsal-disable-widgets', ''),
(7, 'wsal-plugin-viewers', ''),
(8, 'wsal-plugin-editors', ''),
(9, 'wsal-excluded-users', ''),
(10, 'wsal-excluded-roles', ''),
(11, 'wsal-excluded-custom', ''),
(12, 'wsal-excluded-ip', ''),
(13, 'wsal-restrict-admins', ''),
(14, 'wsal-disable-refresh', ''),
(15, 'wsal-use-proxy-ip', ''),
(16, 'wsal-filter-internal-ip', ''),
(17, 'wsal-hide-plugin', ''),
(18, 'wsal-delete-data', ''),
(19, 'wsal-datetime-format', '0'),
(20, 'wsal-wp-backend', ''),
(21, 'wsal-columns', '{"alert_code":"1","type":"1","date":"1","username":"1","source_ip":"1","message":"1"}'),
(22, 'wsal-dev-options', '');

Before deleting, the settings page did state “Next Scheduled Cleanup is in 1 min (or Run Manually)” but it clearly wasn’t running, and didn’t clean the table when I ran manually (it just crashed out, whitescreen).

Hi Dima,

That’s really good of you, thank you!

Regards,
Chris

(Just wanted to bump this back to the top, as it’s already shot off the first page!)

https://make.www.ads-software.com/core/2013/09/24/automatic-core-updates/:

If the install uses FTP for updates (and prompts for credentials), automatic updates are disabled
If the install is running as a SVN or GIT checkout, automatic updates are disabled

I’ve only ever seen WP use FTP for updates and prompt for credentials. Doesn’t this mean that 99% of WordPress installation can’t use the automatic update feature?

How else can WP be installed, other than via FTP or SVN? (Or more to the point, how can I make use of the auto-update feature?)

Snap. Not a multisite issue, all my sites are affected, I guess the security on my server prevents auto updates?

Google brings me to this page first so I will investigate and post back.

Wicked! Thank you! ??

Hi MichaelH,

Thanks for taking the time to reply, but that’s just what I posted that isn’t working ??

Thanks,
Chris

Yes, this is a problem, as of this afternoon Kaspersky will flag that trojan error on any pages where Thickbox is used, even at the original source: https://jquery.com/demo/thickbox/

I have used Thickbox extensively through client sites throughout the years, so will be looking into this problem