Forum Replies Created

Viewing 15 replies - 46 through 60 (of 83 total)
  • Did you remove the page title by using this code?

    .entry-title, .entry-title a {
        display: none;
    }

    Try following code and see the result:

    .td-post-title {
        display: none;
    }

    Are you able to resolve this issue? If you have done it, please share your solution with the community.

    You could target elements on that page only using the class page-id-26470 which is unique to your AMFM EXCLUSIVE VIDEO 2 page.

    Following code will remove the complete header and footer from the given page:

    body.page-id-26470 .top-bar, /* top bar - containing trending notifications and search bar */
    body.page-id-26470 #main-head, /* header - containing logo and navigation bar */
    body.page-id-26470 .breadcrumbs-wrap, /* bread crumbs */
    body.page-id-26470 .main-footer { /* footer */
    	display: none;
    }

    Don’t edit the theme files directly, otherwise your changes will be overwritten whenever the theme is updated.

    Since you’re already using Jetpack, an easy way to add custom CSS is to activate the Custom CSS module. You’ll then add your custom CSS in the new stylesheet editor that’ll appear in your dashboard, under Appearance > Edit CSS.

    As alternatives, you could either install a standalone custom CSS plugin, or create a child theme.

    Thanks for the idea, Steve.

    In response to a similar question, bbpress moderator Stephen Edgar recommends

    You should look to a WordPress plugin for this, not specificly bbPress.

    You should look at using a 3rd party email provider for this to ensure your emails sent to 22k user is not flagged as spam as there will be a high change it will if you do yourself unless you do it over the space of a few days in batches.

    E.g. Start from here and find one that can do what you are looking for:
    https://wordpress.org/plugins/search.php?q=mass+email

    Source

    As you can access the phpMyAdmin from your host panel, it means you can also access the File Manager. If you are unable to login to phpMyAdmin, then you can reset your plugins folder via FTP or the file manager provided in your host’s control panel.

    1. Via FTP or your host’s file manager, navigate to the wp-contents folder (directory)
    2. Via FTP or your host’s file manager, rename the folder “plugins” to “plugins.hold”
    3. Login to your WordPress administration plugins page (/wp-admin/plugins.php) – this will disable any plugin that is “missing”.
    4. Via FTP or your host’s file manager, rename “plugins.hold” back to “plugins”
    Forum: Fixing WordPress
    In reply to: post title problem

    Could you try to replace the 30 with ۳۰ in your post title?

    Are you removing the Yoast SEO plugin nags & notifications by using some code in your theme’s function.php file? Please check line 29 of the functions.php of your active theme (mymetmedia). The code might be similar to the following:

    remove_action( 'admin_notices', array( Yoast_Notification_Center::get(), 'display_notifications' ) );
    remove_action( 'all_admin_notices', array( Yoast_Notification_Center::get(), 'display_notifications' ) );

    If you find these lines, then please remove it and test your website again.

    To be on the safe side, please take a backup of functions.php before editing it.

    Forum: Fixing WordPress
    In reply to: My site is down

    Your site is throwing Internal Server Errors (error 500) are often caused by plugin or theme function conflicts. As you don’t have access to your admin panel, try manually resetting your plugins (no Dashboard access required). If that resolves the issue, reactivate each one individually until you find the cause.

    If that does not resolve the issue, try switching to the default theme for your version of WordPress to rule-out a theme-specific issue. If you don’t have access to your admin panel, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, navigate to /wp-content/themes/ and rename the directory of your currently active theme. This will force the default theme to activate and hopefully rule-out a theme-specific issue.

    If that does not resolve the issue, it’s possible that a .htaccess rule could be the source of the problem. To check for this, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, and rename the .htaccess file. If you can’t find a .htaccess file, make sure that you have set your SFTP or FTP client to view invisible files.

    If you weren’t able to resolve the issue by either resetting your plugins and theme or renaming your .htaccess file, we may be able to help, but we’ll need a more detailed error message. Internal server errors are usually described in more detail in the server error log. If you have access to your server error log, generate the error again, note the date and time, then immediately check your server error log for any errors that occurred during that time period. If you don’t have access to your server error log, ask your hosting provider to look for you.

    Internal server errors (error 500) are often caused by plugin or theme function conflicts, so if you have access to your admin panel, try deactivating all plugins. If you don’t have access to your admin panel, try manually resetting your plugins (no Dashboard access required). If that resolves the issue, reactivate each one individually until you find the cause.

    If that does not resolve the issue, try switching to the default theme for your version of WordPress to rule-out a theme-specific issue. If you don’t have access to your admin panel, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, navigate to /wp-content/themes/ and rename the directory of your currently active theme. This will force the default theme to activate and hopefully rule-out a theme-specific issue.

    If that does not resolve the issue, it’s possible that a .htaccess rule could be the source of the problem. To check for this, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, and rename the .htaccess file. If you can’t find a .htaccess file, make sure that you have set your SFTP or FTP client to view invisible files.

    If you weren’t able to resolve the issue by either resetting your plugins and theme or renaming your .htaccess file, we may be able to help, but we’ll need a more detailed error message. Internal server errors are usually described in more detail in the server error log. If you have access to your server error log, generate the error again, note the date and time, then immediately check your server error log for any errors that occurred during that time period. If you don’t have access to your server error log, ask your hosting provider to look for you.

    You can achieve this by using Thumbnail Upscale plugin.

    Screenshot Example
    Before using the plugin

    After using the plugin

    Your website is hidden behind the Coming Soon Page and not publicly accessible. We need to check the website in order to troubleshoot the issue and suggest the solution.

    Did you change anything recently on your website? A common list of changes that may result in such behavior are:

    • updating the WooCommerce plugin
    • updating the currently active theme
    • installed a new plugin
    • deactivate or remove a plugin
    • change in the css

    I am following this thread and if you need any further help, please write back here.

    Due to the differences between the free hosted blogs offered at wordpress.com and the self-hosted and self-installed version of WordPress supported here, you should probably post WordPress.com Support instead.

    Forum: Plugins
    In reply to: Phone views being hacked

    Remain calm and carefully follow this guide. When you’re done, you may want to implement some (if not all) of the recommended security measures.

    Sharing your website link is a good idea. It will help the plugin/theme author and/or volunteers to troubleshoot the problem and suggest the solution. 🙂

    I am following this thread and if you need further help, please write back here.

    Are you using any tracking plugin to track the leads?

    utm_source=email&utm_medium=email is a tracking code added by the lead tracking plugin.

    You need to check the server logs and iThemes Security log to see which file(s) are they tried to access. Getting these emails mean iThemes Security is taking care of blocking such attempts.

    As you figured out the solution and updated the post, please mark this topic resolved. Thank you.

Viewing 15 replies - 46 through 60 (of 83 total)