Future not displaying on Custom Post Type

  • Resolved guerre64

    (@guerre64)


    10 months, 2 weeks ago

    I am hiding various menu items from the Client using a plugin – Future shows on the standard WP posts area as a metabox on the right hand side. but in the custom post type “Events”, when you edit an event, Future’s metabox is not displaying.

    What could be wrong – it is not a permissions thing with the EasyHide function, but something else, otherwise the Future metabox would not display on standard posts.

    I have Future enabled for the Custom Post type.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter guerre64

    (@guerre64)

    Image of issues on the Future dashboard:

    https://app.screencast.com/xhq672bZ702fW

    Plugin Support Riza Maulana Ardiyanto

    (@rizaardiyanto)

    Hi @guerre64

    Thanks for contacting PublishPress Future.

    Can you please copy your Site Health information here?

    Thanks,

    Thread Starter guerre64

    (@guerre64)

    ` wp-core

version: 6.5.2
site_language: en_AU
user_language: en_AU
timezone: Australia/Melbourne
permalink: /%postname%/
https_status: true
multisite: false
user_registration: 0
blog_public: 0
default_comment_status: open
environment_type: production
user_count: 3
dotorg_communication: true wp-paths-sizes

wordpress_path: /home/revocujate6816/web/twisk-bricks.instawp.xyz/public_html
wordpress_size: 59.76 MB (62662499 bytes)
uploads_path: /home/revocujate6816/web/twisk-bricks.instawp.xyz/public_html/wp-content/uploads
uploads_size: 16.46 MB (17262772 bytes)
themes_path: /home/revocujate6816/web/twisk-bricks.instawp.xyz/public_html/wp-content/themes
themes_size: 44.83 MB (47004051 bytes)
plugins_path: /home/revocujate6816/web/twisk-bricks.instawp.xyz/public_html/wp-content/plugins
plugins_size: 180.99 MB (189778155 bytes)
database_size: 31.17 MB (32686080 bytes)
total_size: 333.21 MB (349393557 bytes) wp-active-theme

name: Bricks Child Theme (bricks-child)
version: 1.1
author: Bricks
author_website: https://bricksbuilder.io/
parent_theme: Bricks (bricks)
theme_features: core-block-patterns, widgets-block-editor, automatic-feed-links, title-tag, html5, menus, post-thumbnails, align-wide, widgets
theme_path: /home/revocujate6816/web/twisk-bricks.instawp.xyz/public_html/wp-content/themes/bricks-child wp-parent-theme

name: Bricks (bricks)
version: 1.9.8
author: Bricks
author_website: https://bricksbuilder.io/
theme_path: /home/revocujate6816/web/twisk-bricks.instawp.xyz/public_html/wp-content/themes/bricks wp-plugins-active (24)

Admin Columns Pro: version: 6.4.8, author: AdminColumns.com
Admin Menu Editor Pro: version: 2.24.2, author: Janis Elsts
Advanced Custom Fields PRO: version: 6.2.9, author: WP Engine
Automatic.css: version: 2.8.3, author: Kevin Geary, Matteo Greco
BricksExtras: version: 1.5.1, author: BricksExtras
BricksUltimate: version: 1.6.4, author: Paul Chinmoy
Duplicate Page: version: 4.5.3, author: mndpsingh287
EWWW Image Optimizer: version: 7.6.0, author: Exactly WWW
Frames: version: 1.4.7, author: Kevin Geary, Matteo Greco
HappyFiles Pro: version: 1.8.3, author: Codeer
JetSearch: version: 3.4.1, author: Crocoblock
Microthemer: version: 7.2.4.9, author: Themeover
PostX: version: 4.0.4, author: Post Grid Team by WPXPO
PostX Pro: version: 1.6.6, author: wpxpo
PublishPress Future: version: 3.3.1, author: PublishPress
Simple History: version: 4.15.1, author: P?r Thernstr?m
SureFeedback Client Site: version: 1.2.3, author: Brainstorm Force
UpdraftPlus - Backup/Restore: version: 2.24.3.26, author: UpdraftPlus.Com, DavidAnderson
User Switching: version: 1.7.3, author: John Blackbourn & contributors
WordPress Importer: version: 0.8.2, author: wordpressdotorg
WP Care Plan: version: 2.0.2, author: WP Care Plan
WPCodeBox 2: version: 1.1.0, author: WPCodeBox
WP Grid Builder: version: 1.9.0, author: Lo?c Blascos
WP Grid Builder - Bricks: version: 1.3.0, author: Lo?c Blascos wp-plugins-inactive (3)

Advanced Themer for Bricks: version: 2.5.3, author: Maxime Beguin
Rank Math SEO PRO: version: 3.0.38, author: Rank Math
Rank Math SEO with AI Best SEO Tools: version: 1.0.218, author: Rank Math wp-media

image_editor: EWWWIO_Imagick_Editor
imagick_module_version: 1690
imagemagick_version: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
imagick_version: 3.7.0
file_uploads: 1
post_max_size: 64M
upload_max_filesize: 64M
max_effective_size: 64 MB
max_file_uploads: 20
gd_version: 2.3.3
gd_formats: GIF, JPEG, PNG, WebP, BMP, XPM
ghostscript_version: unknown wp-server

server_architecture: Linux 5.4.0-153-generic x86_64
httpd_software: Apache/2.4.57 (Ubuntu) mod_fcgid/2.3.9 OpenSSL/1.1.1f
php_version: 7.4.33 64bit
php_sapi: fpm-fcgi
max_input_variables: 1000
time_limit: 30
memory_limit: 256M
max_input_time: 60
upload_max_filesize: 64M
php_post_max_size: 64M
curl_version: 7.68.0 OpenSSL/1.1.1f
suhosin: false
imagick_availability: true
pretty_permalinks: true
htaccess_extra_rules: false
current: 2024-05-08T07:25:36+00:00
utc-time: Wednesday, 08-May-24 07:25:36 UTC
server-time: 2024-05-08T17:25:33+10:00 wp-database

extension: mysqli
server_version: 10.6.14-MariaDB-1:10.6.14+maria~ubu2004
client_version: mysqlnd 7.4.33
max_allowed_packet: 16777216
max_connections: 151 wp-constants

WP_HOME: undefined
WP_SITEURL: undefined
WP_CONTENT_DIR: /home/revocujate6816/web/twisk-bricks.instawp.xyz/public_html/wp-content
WP_PLUGIN_DIR: /home/revocujate6816/web/twisk-bricks.instawp.xyz/public_html/wp-content/plugins
WP_MEMORY_LIMIT: 40M
WP_MAX_MEMORY_LIMIT: 256M
WP_DEBUG: false
WP_DEBUG_DISPLAY: true
WP_DEBUG_LOG: false
SCRIPT_DEBUG: false
WP_CACHE: false
CONCATENATE_SCRIPTS: undefined
COMPRESS_SCRIPTS: undefined
COMPRESS_CSS: undefined
WP_ENVIRONMENT_TYPE: Undefined
WP_DEVELOPMENT_MODE: undefined
DB_CHARSET: utf8
DB_COLLATE: undefined wp-filesystem

wordpress: writable
wp-content: writable
uploads: writable
plugins: writable
themes: writable
    Thread Starter guerre64

    (@guerre64)

    So, I finally figured this out and it is due to very weird behaviour for the plugin, via its own settings.

    I was having a problem displaying the Future metabox on a CPT, “EVENTS” for the user type of “Editor”.

    The settings in Future are not actually right from my point of view – the “Editor” user type was not enabled in the Advanced tab. Despite this, Future’s metabox was actually visible on the built-in WordPress Posts, but not visible on the CPT, “EVENTS”. Once the “Editor” user type was enabled, then the metabox appeared in the CPT.

    This is completely counter-intuitive – why on earth would the Future metabox be visible for Editors in normal WordPress posts when the “Editor” user type is not enabled??????? This makes no sense at all and it is no wonder that it took me so long to actually find this glaring fault.

    Screenshot: https://app.screencast.com/gdow9RP8lG6tb

    • This reply was modified 10 months, 2 weeks ago by guerre64.
    Plugin Support Riza Maulana Ardiyanto

    (@rizaardiyanto)

    @guerre64 You are correct about this. This is an issue with our plugin and I have created a GitHub issue on it so our developer can fix it in the future release: https://github.com/publishpress/PublishPress-Future/issues/727

    Thanks,

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Future not displaying on Custom Post Type’ is closed to new replies.