Skip Navigation

[Resolved] Toolset Access shortcode is blank

This support ticket is created 6 years, 7 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 14:00 – 18:00 13:00 – 18:00 -

Supporter timezone: America/Jamaica (GMT-05:00)

This topic contains 6 replies, has 3 voices.

Last updated by Shane 6 years, 7 months ago.

Assisted by: Shane.

Author
Posts
#804472

I am trying to: add a "add" button linking to add page which should not be visible to users who can't add.

[toolset_access role="Administrator,Editor,Author,Players Editor" operator="allow"]hidden link" role="button" class="btn btn-primary btn-lg pull-right" style="color: white;">Add Team <br>[/toolset_access]

Link to a page where the issue can be seen: hidden link

I expected to see: a button

Instead, I got: blank

#805233

Hi, can you try the following troubleshooting steps first?
- Temporarily remove the toolset_access shortcodes and check to be sure the link appears as expected
- Temporarily activate a default theme like Twenty Seventeen, then deactivate all plugins except Types, Views, and Access, then test again.
- If the problem was resolved, reactivate your theme and plugins one by one until the conflict returns. Let me know what you find out.
- If the problem was not resolved, continue.
- Are the results the same for all User roles, or only one specific User role?
- Where have you placed this shortcode? Is it in an area that does not support shortcodes at all? For instance, if you insert the [wpv-post-title id='$current_page'] shortcode, what do you see?

#875188

It works here: hidden link

So it must be a theme issue; not surprising given the situation of the theme in that site.

Can you tell me what might be needed to make this work?

#875189

I forgot to mention. Since the base theme is bad, I'm using a different template for this: archive-team.php which is basically a 27 copy.

<?php
/**
 * The template for displaying archive pages
 *
 * @link https://codex.wordpress.org/Template_Hierarchy
 *
 * @since 1.0
 * @version 1.0
 */

get_header(); ?>

<div class="wrap">

	<?php if ( have_posts() ) : ?>
		<header class="page-header">
			<?php
				the_archive_title( '<h1 class="page-title">', '</h1>' );
				the_archive_description( '<div class="taxonomy-description">', '</div>' );
			?>
		</header><!-- .page-header -->
	<?php endif; ?>

	<div id="primary" class="content-area">
		<main id="main" class="site-main" role="main">

		<?php
		if ( have_posts() ) : ?>
			<?php
			/* Start the Loop */
			while ( have_posts() ) : the_post();
            echo get_post_format();
				/*
				 * Include the Post-Format-specific template for the content.
				 * If you want to override this in a child theme, then include a file
				 * called content-___.php (where ___ is the Post Format name) and that will be used instead.
				 */
?>
                <article id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
                <?php
                // if ( is_sticky() && is_home() ) :
                // 	echo twentyseventeen_get_svg( array( 'icon' => 'thumb-tack' ) );
                // endif;
                ?>
                <header class="entry-header">
                    <?php
                    if ( 'post' === get_post_type() ) {
                        echo '<div class="entry-meta">';
                            if ( is_single() ) {
                                twentyseventeen_posted_on();
                            } else {
                                echo twentyseventeen_time_link();
                                twentyseventeen_edit_link();
                            };
                        echo '</div><!-- .entry-meta -->';
                    };
            
                    if ( is_single() ) {
                        the_title( '<h1 class="entry-title">', '</h1>' );
                    } elseif ( is_front_page() && is_home() ) {
                        the_title( '<h3 class="entry-title"><a href="' . esc_url( get_permalink() ) . '" rel="bookmark">', '</a></h3>' );
                    } else {
                        the_title( '<h2 class="entry-title"><a href="' . esc_url( get_permalink() ) . '" rel="bookmark">', '</a></h2>' );
                    }
                    ?>
                </header><!-- .entry-header -->
            
                <?php if ( '' !== get_the_post_thumbnail() && ! is_single() ) : ?>
                    <div class="post-thumbnail">
                        <a href="<?php the_permalink(); ?>">
                            <?php the_post_thumbnail( 'twentyseventeen-featured-image' ); ?>
                        </a>
                    </div><!-- .post-thumbnail -->
                <?php endif; ?>
            
                <div class="entry-content">
                    <?php
                    /* translators: %s: Name of current post */
                    the_content( sprintf(
                        __( 'Continue reading<span class="screen-reader-text"> "%s"</span>', 'twentyseventeen' ),
                        get_the_title()
                    ) );
            
                    wp_link_pages( array(
                        'before'      => '<div class="page-links">' . __( 'Pages:', 'twentyseventeen' ),
                        'after'       => '</div>',
                        'link_before' => '<span class="page-number">',
                        'link_after'  => '</span>',
                    ) );
                    ?>
                </div><!-- .entry-content -->
            
                <?php
                // if ( is_single() ) {
                // 	twentyseventeen_entry_footer();
                // }
                ?>
            
            </article><!-- #post-## -->
<?php            
			endwhile;

            the_posts_pagination( array(
				'prev_text' => twentyseventeen_get_svg( array( 'icon' => 'arrow-left' ) ) . '<span class="screen-reader-text">' . __( 'Previous page', 'twentyseventeen' ) . '</span>',
				'next_text' => '<span class="screen-reader-text">' . __( 'Next page', 'twentyseventeen' ) . '</span>' . twentyseventeen_get_svg( array( 'icon' => 'arrow-right' ) ),
				'before_page_number' => '<span class="meta-nav screen-reader-text">' . __( 'Page', 'twentyseventeen' ) . ' </span>',
			) );

		else :

            get_template_part( 'template-parts/post/content', 'none' );

		endif; ?>

		</main><!-- #main -->
	</div><!-- #primary -->
	<?php get_sidebar(); ?>
</div><!-- .wrap -->

<?php get_footer();

#880762

I don't see anything obvious in the template file that would cause a conflict with Toolset Access inline controls, so there must be something else going on. It could be a conflict in the theme, or a configuration issue. Here's what I would check next:
- Remove the custom role "Players Editor" from the inline control shortcode and test again.
- If Admins are now able to see the link, then I would run some tests with a Players Editor User. Publish at least one post as the Players Editor User, then test the inline control shortcode again with the Players Editor role in place.
- Display each User's role on the front-end of the site using the wpv-current-user shortcode:

[wpv-current-user info='role']

Check to be sure the role shown there is what you expect. It should be a sanitized version of the role you see in Access.

#885665
Capture.PNG

thank you. i will check later and let you know.

in the mean time, is toolset incompatible with ckeditor? any solution?

I have to disable cke everytime.

#889370

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hello,

As Christian is currently on vacation I will be handling this ticket.

Unfortunately I cannot speak on the compatibility however I do know that we use the Default TinyMCE editor that wordpress uses for their editor.

Thanks,
Shane