Forum Replies Created

Viewing 15 replies - 1 through 15 (of 177 total)
  • Thread Starter Ben Greeley

    (@bengreeley)

    I was only testing with the headings in core, but you’re right – it doesn’t seem like bolding in markdown or links are supported in core. Since headings aren’t supported in the forums, that makes sense why they don’t appear. So we’d need to install some sort of block plugin to support markdown to achieve this or wait core Gutenberg has full support.

    Thanks for humoring me, John!

    Thread Starter Ben Greeley

    (@bengreeley)

    When I test, such as starting a paragraph with # to convert to heading or **text** for bold it doesn’t seem to convert to the appropriate block (such as in this forum thread). When I do the same in the editor in WordPress it automatically does a conversion when I type.

    Perhaps when I save it’ll do a conversion for me, but I haven’t seen it happen automatically yet. Are you able to paste markdown in the forums?

    Thread Starter Ben Greeley

    (@bengreeley)

    OK, thank you! I’ll look into seeing if we’ve disabled this somehow in the wordpress.org support forums.

    I’m glad you were able to figure it out!

    My only advice is to make sure WP-CLI is something you can use on your hosting environment before digging into it. Some hosting companies don’t provide SSH access or ways to run WP-CLI commands so you may want to look into their support first.

    This one might be difficult to troubleshoot, but if you could look at the permissions level on your htaccess and add it to the thread (it should be a 3-digit number) or take a screenshot, I can try to walk you through how to change it if it’s needed.

    Alternatively, this might be something better-suited for your hosting company to help you with if you’re not able to modify your .htaccess file. Some hosting companies lock down those files, so you may need their assistance.

    @csuk There is likely some code in your theme or in a plugin that is making it show logged out. I’d recommend opening the functions.php file in the theme and see if add_filter( 'show_admin_bar', '__return_true' ); is anywhere in the file.

    If you don’t see it, try adding add_filter( 'show_admin_bar', '__return_false', 9999 ); to the theme functions.php file. This should disable the admin bar when people are logged out.

    I hope that helps.

    That sounds like a file permission issue on .htaccess which is preventing you to save to it. You may need to get in touch with your hosting company about getting permission to modify the file. You could try changing the permission to 644, which will allow the owner of the file to read/write. You could temporarily change the permissions higher until you can write to the file but you’ll want to make sure it’s back to 644 after editing for security reasons.

    Forum: Fixing WordPress
    In reply to: Quarantined

    @nudgephelps Sorry to hear about your woes with files being quarantined. It’s possible a plugin or another service had a bug that was exploited. The most important thing to do at this point is to identify and try to remove the files that were added and are being quarantined and then try to identify what may have caused the vulnerability.

    Carefully follow this guide. When you’re done, you may want to implement some (if not all) of the recommended security measures and start backing up your site.

    @edcarlson This sounds like a conflict with a plugin or theme. Since you’re using a default theme, that’s probably not the case, so I’d recommend starting by disabling all plugins and then enabling them one by one to see if you are able to reproduce the issue. This will help you pinpoint which plugin is causing the issue (if it’s a plugin error).

    Do your server error logs show any errors? That might help pinpoint where the issue is coming from as well.

    That’s great that you were able to get it working!

    @atifnawaz Apologies if this is too basic of a recommendation, but have you tried pasting the WordPress code for .htaccess into .htaccess and replace what’s there? You could make a backup of .htaccess and test it out and if it doesn’t work, revert back to the original code.

    @familyworldhub It’s not clear what may have caused the database tables to be unavailable, but you can try running the database repair tool at https://familyworldhub.com/wp-admin/maint/repair.php . It should be able to walk you through the process.

    @ico22 At first glance at your robots.txt, I noticed that / isn’t on the ‘Allow’ section, only /wp-admin/admin-ajax.php (which Google shouldn’t index anyways). I’m not familiar with AISEO, but if you’re able to modify the robots.txt to remove that directory and add / in its place, I think this may resolve your issue.

    Otherwise, that page is returning a 200 code which is good, so my guess is it’s the contents of the robots.txt that it doesn’t like vs being unable to reach it. There’s also a tool in Google Webmaster Tools of ‘Fetch as Googlebot’, which maybe you can use to troubleshoot how Google is viewing the file.

    Best of luck.

    Thank you for providing the screenshots @digital2019. At first glance, I see the author and category fields unless I’m missing something. I do see what you mean about the featured image not being available. I wonder if it’s further down the screen, as it seems the items are out of order. If you scroll down in that panel, do you see the options? See a screencast from my computer: https://d.pr/i/sR80lm You could also try zooming out in your browser and see if it appears if you’re not able to scroll. Go to ‘View’ -> ‘Zoom Out’ in your browser.

    If the featured image panel is still missing after taking those steps, it’s possible something happened in your theme that is making featured images incompatible. If you feel comfortable with code, you could check if your theme’s functions.php file contains add_theme_support( 'post-thumbnails' ); if not, add it.

    Hopefully, you’re able to get to the bottom of this soon.

Viewing 15 replies - 1 through 15 (of 177 total)