Spectacula

I’ve just had the same problem come up for me but with 90+ authors/editors/admins all suddenly seeing no editor. Coincidentally we’d just activated CloudFront and after stepping over a few possible things like cross-origin and missing JS I chose to trace the code and found the problem.

Turns out the problem was down to the UserAgent string being sent to WordPress by CloudFront. If WP doesn’t recognise the string you don’t get a fancy editor. We modified CloudFront such that the UA for admins would be untouched and everything came back. The other option would be a plugin that does the following:

add_filter( 'user_can_richedit', function( $wp_rich_edit ) {
    if ( !$wp_rich_edit
         && ( get_user_option( 'rich_editing' ) == 'true' || !is_user_logged_in() )
         && isset( $_SERVER[ 'HTTP_USER_AGENT' ] )
         && stripos( $_SERVER[ 'HTTP_USER_AGENT' ], 'amazon cloudfront' ) !== false
    ) {
        return true;
    }

    return $wp_rich_edit;
} );

From the sound of things the first poster’s problem machine may have a firewall/privacy/av app that’s modifying the UserAgent so you could take the above code and change the “amazon cloudfront” string to match part of your UA and all should be well.

• This reply was modified 6 years, 6 months ago by Spectacula.

Thank you so much for fixing this so quickly..

Turns out I underestimated the amount of data per user coming from the options table. Option table load has gone from 14MB per user to 150KB per user, a slight improvement ??

Thanks,

We’ll patch our db.

This is going to sound a little patronising but can you run through the troubleshooting tips here https://codex.www.ads-software.com/Managing_Plugins#Advanced_Troubleshootings
specifically steps 5 and 6.

As it is I don’t have enough information to go on.

I’ve rolled out another version of spots that should fix this. Sometimes WordPress would have the quotes converted to their html entities and sometimes it would convert then to the numeric equivalent. Shouldn’t be a problem any more.

You may need to go to the spots settings page and change the cache time down to 0 for the fix to show up immediately.

I’ve rolled out a new version (1.3.2) that should fix this issue.

The changes in 4.0.1 also included something that made quotes after a number different from normal quotes. The assumption being that they’re always to denote feet/inches.

The spot’s short code has to run very late in the content process to avoid making a mess of other plug-in and to avoid the same plug-ins making a mess of the spot. So when it came to the parsing the short code the spot ID was now wrapped in mismatched quotes. I’ve added something to fix the quote issue for the short code.

I’ve also added some extra checks in the short code that’ll ensure that the ID is always a numeric value so future breaks will just cause the spot to vanish rather than leave broken fragments and possibly causing confusion.

Ignore the above.
I’ve gone and released version 1.3.1.

Hi,

If you go to https://www.ads-software.com/plugins/spots/developers/ and download the developer version that problem should go away. I was hoping to have that version live a while ago but other projects have held me up.

There are no filters around the spot widget content so the widget_text filter isn’t going to work. That is generally for the default WordPress text widget.

If you view the spot on it’s own page does it show the content of the short code? If it doesn’t then there’s something wrong with you post formatting or the short code may not run on anything but the post post_type. To view it on its own page edit it in the full editor then click the view button.

If you still have problems it could be that the short code isn’t registered at the point it is called. Adding something like this near where the spot is being called will dump the list of short code tags into your error log.

global $shortcode_tags;
error_log( var_export( $shortcode_tags, true ) );

If your needed one isn’t in there then that’s the problem. I can’t tell you if the above code will work for you but the basic idea is solid.

It should work with shortcodes but that is really down to the individual shortcode that you’re trying to use. If that shortcode isn’t registered at the time the spot tries to call it or there’s something wrong with the formatting of the shortcode in the spot you’ll get what you’re seeing. I don’t know this shortcode you’re using so can’t really help with specifics.

We place our shortcode very late in the running order to avoid nasty interactions with others and it would seem they’re doing the same thing. The only thing I can recommend involves you editing the code:
You can try changing line 66 of icit-spots.php from
add_filter( 'the_content', array( $this, 'late_shortcode' ), 9999999 );
to
add_filter( 'the_content', array( $this, 'late_shortcode' ), 9996 );
This should have our shortcode fire before theirs but after everyone else’s.

When the header fires you don’t know if there’s a need to show the styles yet or not. Only once a shortcode fires do you know if you need them or not. We’re doing some updates to the spots plug-in at the moment I’ll see what I can do to change this. Probably just move the style to header if logged in with an editor level or above account. unfortunately other work takes precedents so I can’t say how long it’ll be before I complete the next version of it.

I’ve committed a new version with a filter that will allow you to disable the edit button. As of version 1.3 adding:
add_filter( 'spots_show_edit_link', '__return_false' );
to you theme’s functions.php will remove the edit link.

I’ve not yet marked it as a stable release so you’ll have to download trunk. https://downloads.www.ads-software.com/plugin/spots.zip
The reason I’ve not yet marked it as stable is that there are other changes in there that I’ve not had a chance to test on older versions of WordPress. However, if you’re running with 3.9 everything should be good.

I’ve release version 1.2.2 that fixes that problem. By fixed, I mean I’ve rolled back a bit of code I modified because it looked ugly without remembering why it looked so ugly. ??

If I understand you correctly you just need to drop something like this:

<?php
if ( function_exists( 'icit_spot' ) )
    icit_spot( 'Title of the spot' );
?>

Into your template.