Support » Plugin: Content Mask » Disable content mask for some custom post types

  • Resolved 1000camels

    (@1000camels)


    I am seeing errors on pages not using content mask.

    PHP Notice:  Undefined index: content_mask_enable in /wp-content/plugins/content-mask/content-mask.php on line 1633
    [25-May-2021 05:24:14 UTC] PHP Notice:  Undefined index: content_mask_role_permissions in /wp-content/plugins/content-mask/content-mask.php on line 1637
    [25-May-2021 05:24:14 UTC] PHP Notice:  Undefined index: content_mask_condition_permissions in /wp-content/plugins/content-mask/content-mask.php on line 1638

    Is there a way to disable the plugin for specific custom post types?

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Xhynk

    (@alexdemchak)

    Currently there’s not a way to disable it for Custom Post Types, but that’s actually a great idea – I’ll work on an update and get that added in there ASAP!

    As for the errors, you may have WP_DEBUG mode or error_reporting enabled. However those are also errors I can account for in the plugin itself. Give me a few moments and I’ll get a preliminary update out that fixes that

    Thread Starter 1000camels

    (@1000camels)

    Great. Thank you. A filter would be sufficient, and perhaps even preferable.

    Plugin Author Xhynk

    (@alexdemchak)

    I pushed out an update to version 1.8.2.4 that should a) prevent those warnings from showing, and b) added a “Post Type” selector in the Content Mask > Options page for all public post types.

    Clicking on the X for a Post Type will now hide the Content Mask meta box on the editor page, as well as prevent any page-processing for that post type on the front end.

    Let me know if anything isn’t working as expected!

    Thread Starter 1000camels

    (@1000camels)

    Thank you for being so responsive.

    Unfortunately, there appears to be a little issue with the XHR saving. It doesn’t always fire. I can see when the icon indicates progress and then I know it works, but that doesn’t always trigger. Not sure what is happening.

    Plugin Author Xhynk

    (@alexdemchak)

    Would you be able to send a video of exactly what’s happening? Also if you open Dev Tools (F12 in Chrome), go to the Network Tab, and click on the icon, it should make a single XHR request that shows up in your logs: https://www.loom.com/share/ee00d4e47f474ce4bbd3278c44906aa6?from_recorder=1&focus_title=1

    Can you let me know what that log shows? It should show a simple JSON payload of “Content Masking now [state] for [post_type]” with a status of 200. It may be receiving “No Values Detected” or “Unauthorized Values Detected”

    Also if you could right click on one of them (that’s not working ideally) and choose inspect element, and send me a screenshot of it like this (fully opened in the element tree view) that would be helpful! https://i.imgur.com/DZuSceY.png

    I’ve installed the new update on a handful of new sites, including localhost sites, and every request has gone through as intended to enable/disable it.

    You can send those screenshots/video links/anything else to me at info@xhynk.com and I’ll be happy to take a look!

    Thread Starter 1000camels

    (@1000camels)

    I went to produce the screen capture and it is working. It was simply not firing the javascript (no XHR), so I assume it was a cached js file that was the issue.

    Thread Starter 1000camels

    (@1000camels)

    I am returning to this, because I noticed that there are several custom post types, notably shop_orders from Woocommerce that do not appear in the list of types to disable it for. It ends up creating extra metadata for all those Orders.

    Would be great if this list was opt-in for all but Posts and Pages.

    Plugin Author Xhynk

    (@alexdemchak)

    I’ve pushed an update out (1.8.2.8) that prevents the save_meta function from doing anything on any post type that’s not considered “publicly viewable” – this should prevent the additional metadata from being saved when not necessary, thanks for pointing that out!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Disable content mask for some custom post types’ is closed to new replies.