Keith Taylor

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 42 total)
  • Author
    Posts
  • in reply to: Annoying Yoast SEO Updated message #2837

    Keith Taylor
    Keymaster
    Ŧollars: Ŧ 1 ,190.26



    It looks like Yoast SEO notification messages are annoying more than just you and I!

    I googled hide yoast admin notices and among many results, I found the very useful WordPress plugin: Yoast SEO Disable Notifications. That’s an archive link, so future visitors might like to see if there are any updates to that plugin.

    Note that, though it is described as a Multi User plugin it works on normal single site WordPress as well as MultiSite. I’ve started adding it to all my websites. For those who just want the snippet for Code Snippets or Functionality, just copy and paste:

    add_action('admin_init', 'wpc_disable_yoast_notifications');
    function wpc_disable_yoast_notifications() {
      if (is_plugin_active('wordpress-seo/wp-seo.php')) {
        remove_action('admin_notices', array(Yoast_Notification_Center::get(), 'display_notifications'));
        remove_action('all_admin_notices', array(Yoast_Notification_Center::get(), 'display_notifications'));
      }
    }
  • in reply to: Broken MesoColumn WordPress Theme #2830

    Keith Taylor
    Keymaster
    Ŧollars: Ŧ 1 ,190.26

    Thanks Anna for the private message via the orange Internet Help button. With the site login details, I’ve fixed this now.

    To fix it, I recreated a new child using Orbisius Child Theme Creator, the re-applied the child customizations using Orbisius Child Theme Editor. I also had to re=apply the color changes through Customizer.

    Fortunately, these changes were small. For an extensively customized theme, I would have recommended restoring the previous version of MesoColumn, then proceeding more carefully.

    To avoid this in future, I always recommend checking what has changed before you update WordPress Themes. This is slightly harder than checking WordPress plugin changes. I’ll do more in-depth notes about this in the website guidelines. A rough guide is:

    1. Goto Admin-Appearance and look for the parent theme that has an update available.
    2. Click on Details, then click View version N.n details where N.n is the new version number.
    3. Scroll down, and click Development Log under ‘Browse the Code’.
    4. There are lots of ways to explore the WordPress Theme Development Log. We are looking for details of the changes since the last version. 1 easy way is to click the revision number next to the latest change at the top of the list of versions.
    5. Click the folder of the latest version. Then browse the file list. Excellent themes will have a file called changelog.txt. Good themes might record the changelog details within the readme file.

    If you are uncertain, please start a new topic here with your theme name, and the old version number. I will check if significant changes are likely to affect your website.

    Do you want to be absolutely certain that changes to WordPress themes will not adversely affect the look and feel of your website? Talk to me about setting up a staging area for you. This is a working copy of your website with a different address. It allows you to test radical changes to your website before you commit to changing your live site.

  • in reply to: Yoast Permalinks Options #2740

    Keith Taylor
    Keymaster
    Ŧollars: Ŧ 1 ,190.26

    Hey, thanks for bringing these Yoast SEO advanced options to my attention. You should know that the main reason I use this plugin in my WordPress sites is for the sitemap. I talk about that elsewhere, but if you’re not sure why, please just ask. I think you should only use SEO techniques to improve visitor experience. SEO is largely meaningless, and dangerous if it deflects you from servicing your audience.

    One side effect of the default Permalinks settings for Yoast SEO, is the increase in 404 errors. This is especially true for Shortlinks in the <head> section. I can’t see the value in them, and they become a problem in superseded posts because it’s something else to redirect. I’m changing my installation routine to hide Shortlinks for Posts.

    RSS links are normally a good thing to keep. Note that I use FeedBurner, and I should include this in the <head>. If this is something that is important to you now, please raise it as a seperate support topic.

    RSD means ‘Real Simple Discovery.’ I don’t understand why the default is ‘Show.’ I recommend changing it to ‘Hide’ as it is only useful if you post to your blog from third party services (which I definitely do not recommend).

    WLW refers to ‘Windows Live Writer.’ Again, I do not recommend that service, and so you should change the Yoast SEO default to ‘Hide.’

    My response to the ‘Remove the ?replytocom variables’ harks back to my opening comments. It is not important for most websites, so best ignored. It only relates to websites with valuable comments. I prefer to encourage debate using the forums. Therefore, I recommend leaving this option alone. It only needs to be considered if ?replytocom links are occurring in error reports from Google Search Console, or similar. If you’re having this type of issue, it’s best to raise it as a separate topic.

    Thanks again for raising this issue. I hope hiding RSD links, WLW Manifest links, and shortlinks decreases 404 errors for you. It might take several months for robots to stop seeking these unimportant links. Please let me know how it affects your website.

  • in reply to: FeedBurner subscription form failed to import #2732

    Keith Taylor
    Keymaster
    Ŧollars: Ŧ 1 ,190.26



    I’ve finally got round to sorting this out. Or, I think I’ve sorted it out. I’ll be testing the following fix on new WordPress Imports, to ensure it catches all problems.

    Please note that the following is quite technical. I don’t expect managed clients to know anything about the following explanation. I’m including it here, in case other visitors want to manage this problem on their own websites. Or, you could just ask me to manage it! 😉

    This failure to import forms is a restriction in WordPress. Even though the Import routine is run by a WordPress Administrator, the input is checked for potential problems. In this case, it’s triggered by the HTML <form> tag. Other problem tags include <iframe> and <embed>.

    I intended trying to find a definitive list. Then, I could search for these, and manually correct them post-import. However, this could get tedious on some websites. What is really required is to stop the Import process filtering out content that has already been accepted.

    The problem lies in a process triggered by wp_filter_post_kses. There is a common ‘solution’ commonly offered to overcome this. Many suggest that the problem can be resolved by hacking the WordPress core file, wp-includes/kses.php:

    #add_filter('content_save_pre', 'wp_filter_post_kses');
    #add_filter('excerpt_save_pre', 'wp_filter_post_kses');
    #add_filter('content_filtered_save_pre', 'wp_filter_post_kses');

    That suggestion is to put # at the beginning of the lines to turn them into comments. Hacking WordPress core is never a good idea. It should definitely not be required in this case. The kses function is made active with add_filter. So, the obvious answer is to cancel that in functions.php, using remove_filter

    Now, the main problem with remove_filter is knowing where to apply it. If you try to remove the kses filter before it is applied, your removal will fail. In this case, the solution is easy.

    We can see from the way that wp_filter_post_kses is called, there is no priority assigned. So, the WordPress default priority of 10 will be applied. All we have to do is specify a higher number for our remove_filter call. Not that higher number = lower priority. To be precise:

    Lower numbers correspond with earlier execution, and functions with the same priority are executed in the order in which they were added to the filter.

    The final result is:

    
    add_action('init','kct_disable_kses',20);
    function kct_disable_kses() {
        add_filter('content_save_pre', 'wp_filter_post_kses');
        add_filter('excerpt_save_pre', 'wp_filter_post_kses');
        add_filter('content_filtered_save_pre', 'wp_filter_post_kses');
    }
    

    Note that, once you’ve Imported your WordPress content, you should disable this little snippet.

  • in reply to: bbPress Slack integration inconsistencies #2726

    Keith Taylor
    Keymaster
    Ŧollars: Ŧ 1 ,190.26

    Yes I can! 😀

    bbPress Slack Webhook Message Limit bbPress Slack Webhook Message Limit: Slack screenshot

    • This reply was modified 3 years, 8 months ago by  Keith Taylor. Reason: Screenshot of Slack messages that got through
    • This reply was modified 3 years, 8 months ago by  Keith Taylor.
    • This reply was modified 3 years, 8 months ago by  Keith Taylor.
    • This reply was modified 3 years, 8 months ago by  Keith Taylor. Reason: bbPress will need tweaking if it is to display WP media with caption!
  • in reply to: bbPress Slack integration inconsistencies #2725

    Keith Taylor
    Keymaster
    Ŧollars: Ŧ 1 ,190.26

    Yippee! 153 is probably enough for my purposes. I only want to know if a message has arrived. Maybe I should have stuck at 153, but I can’t resist one last attempt.

    Can I send 160 characters from a bbPress forum to Slack?

  • in reply to: bbPress Slack integration inconsistencies #2724

    Keith Taylor
    Keymaster
    Ŧollars: Ŧ 1 ,190.26

    Maybe my Twitter thought is relevant? 175 doesn’t work. In desperation I’ll try half way between 131 and 175. Surely, I can have 153 characters? Even Twitter is more generous than that.

  • in reply to: bbPress Slack integration inconsistencies #2723

    Keith Taylor
    Keymaster
    Ŧollars: Ŧ 1 ,190.26

    Nope! 250 too high. And why did the code get scrambled?

    		if ( 250 < strlen( $excerpt ) ) {
    			$excerpt = substr( $excerpt, 0, 250 );
    		}
    

    Let’s try another binary chop at 175.

    I need the character counter check, to make sure my message is bigger than the limit I’m testing.

  • in reply to: bbPress Slack integration inconsistencies #2722

    Keith Taylor
    Keymaster
    Ŧollars: Ŧ 1 ,190.26

    Yo! success! 😀

    I can confirm there is probably a bug in the WordPress JP bbPress Slack Integration plugin. It’s a simple plug-in, which I’ll probably just adopt as a Code snippet. The offending lines are:

    		$excerpt = wp_trim_words( $post->post_content );
    		if ( 100 < strlen( $excerpt ) ) {
    			$excerpt = substr( $excerpt, 0, 100 );
    

    Which started at 500, and failed at 400. 100 is OK, so the next logical attempt is 250.

  • in reply to: bbPress Slack integration inconsistencies #2721

    Keith Taylor
    Keymaster
    Ŧollars: Ŧ 1 ,190.26

    Nope! No success with 400 characters – assuming I’ve hacked the WordPress plugin code OK??!!

    Biggest message I can see that has gone through so far is 131 characters. I wonder if Twitter is an influence here? Let’s try 100, just to test the hacking principle.

  • in reply to: bbPress Slack integration inconsistencies #2720

    Keith Taylor
    Keymaster
    Ŧollars: Ŧ 1 ,190.26

    Whatever the limit is, it seems to be less than 490. Time for a better strategy, so I’ll try 400. If that doesn’t work, I’ll work up from the size of a message that has gone through OK.

    Live troubleshooting in action!

    It’s one of those typical problems with tech. If I new what the limit was called, I might be able to find it. If not, good old trial and error has to work eventually.

    This would be less tedious if the bbPress editor had a character counter. Without that, copy and paste into http://www.charactercountonline.com/ is working.

  • in reply to: Transfer PROSPRA Task Manager Website #2718

    Keith Taylor
    Keymaster
    Ŧollars: Ŧ 1 ,190.26

    OOps! Off-topic. See what happens when you rush me! Never mind. We’re all learning.

  • in reply to: Transfer PROSPRA Task Manager Website #2717

    Keith Taylor
    Keymaster
    Ŧollars: Ŧ 1 ,190.26

    I’m on it!

    Weird, but I seem to be missing alternate update notifications from the forum.

    Anyone else got this issue with bbPress-Slack?

  • in reply to: Transfer PROSPRA Task Manager Website #2714

    Keith Taylor
    Keymaster
    Ŧollars: Ŧ 1 ,190.26

    Fair comment!

    So do we just get on with the forum move? Then you can teach me some brevity as I reduce your WordPress admin burden.

  • in reply to: Managing First Line Support #2710

    Keith Taylor
    Keymaster
    Ŧollars: Ŧ 1 ,190.26

    This is very exciting! I’d better respond in public so that other people can see we’re making progress.

    First line support is working fine, as you know. However, I’ve experienced some notification problems for 2nd line support. I’m working on it today. If all goes well, I’ll have documentation done, and we can all sleep easier!

    Even if it takes a little longer, I’m confident by the end of the week, we’ll have your support needs managed the Shrewdies way. That’s integration of bbPress forum, FreshDesk helpdesk, email, phones, and anything else that springs to mind. (Do you want that web page live chat widget we talked about??!! 🙂 ). It covers message funneling to sales leads, product development, and promotion content improvement (website and print).

    Thanks for letting me develop this with you. I’ll add these commercial website management services to my price list soon. As a thank you for your patience whilst we pulled this together, you will not get charged! Ever! 😀

Viewing 15 posts - 1 through 15 (of 42 total)