Well, I found the solution. Apparently this bug appeared after I made a system update. The reason why I did not connect this bug with a plugin update is because I did not write any new entries on the days after the update. After I deactivated ACF the issue was gone. Apparently the issue also … Read more
Have you updated to the latest version of the WCK – Custom Fields and Custom Post Types Creator plugin? The issue is with the WCK – Custom Fields and Custom Post Types Creator plugin and you should probably seek direct assistance from them. https://wordpress.org/plugins/wck-custom-fields-and-custom-post-types-creator/ When I checked the plugins code (vers. 1.1.5) I can see … Read more
Is there any way to stop this Don’t have JavaScript in your editor. It’s dirty and difficult to maintain (as you’ve found out). Instead, you could: Use a page template Use custom fields (post meta) Use conditional code in your functions.php For 3), as an example: function wpse_202946_script() { if ( is_page( ‘id_or_title_or_slug’ ) ) … Read more
Duh! It was a permissions issue: a folder inside the theme folder (containing all the files triggering the 404 errors) was set to 700 instead of 755.
I found the reason for this problem! The server admin found that the culprit was the suhosin PHP extension. They disabled the extension and replaced it with cagefs.
Your if condition is wrong and generates a syntax error. You need an logical operator to check for multiple conditions. Therefore your code should look like the following: if ( $template_file === ‘page-custom-one.php’ || $template_file === ‘page-custom-two.php’ ) { remove_post_type_support( ‘page’, ‘editor’ ); } You could also check for multiple values with the in_array function … Read more
One solution is to hook into wp_insert_post_data and do some regex magic to replace all instances of & with &: // when saving posts, replace & with & function cc_wpse_264548_unamp( $data ) { $data[‘post_content’] = preg_replace( “/&/”, // find ‘&’ “&”, // replace with ‘&’ $data[‘post_content’] // target the ‘post_content’ ); return $data; } add_filter( … Read more
Array value ‘content_css’ is not enough, TinyMCE can’t simply get the classes from the custom.css file. You need to define the list of styles you want in the dropdown: function my_format_TinyMCE( $in ) { $in[‘content_css’] = get_template_directory_uri() . “/custom.css”; $in[‘importcss_append’] = TRUE; $in[‘style_formats’] = json_encode(array( array(‘title’ => ‘Title for Style #1’, ‘classes’ => ‘example-class’), array(‘title’ … Read more
By default, editors and admins in a single site installation have the unfiltered_html capability, which means they can insert any JavaScript and forms. If you want to disallow that, you can remove that capability from the editor role as described in Why is javascript allowed in my post content? or using a plugin like Members. … Read more
Upgrade visual composes to latest version. Their changelog says latest version is compatible with WordPress 5.0. After upgrading VC you can safely update wordpress core to 5.0.