Lina Asenova

To start, try clearing the Cloudflare cache to ensure that any recent changes are properly reflected on the front end. Additionally, review your configuration settings, as incorrect configurations can lead to unexpected behaviors.

Regarding the console errors you shared, it looks like some scripts related to WooCommerce are being loaded in the wrong order. These scripts need to load in the footer, but they’re being loaded in the header instead. This can happen if a caching or minifying plugin is changing the loading order or if a plugin isn’t properly set up.

To troubleshoot this:

1. Check your caching/minifying plugins: Some of these plugins have options to reorder JavaScript or to minify them. Try disabling JavaScript minification or reordering if it’s enabled, then clear the cache.

2. Ensure plugins are up to date: Sometimes, outdated plugins can lead to compatibility issues. Check if WooCommerce, payment, or other related plugins are up to date.

3. Disable plugins one by one: Temporarily disable your plugins and re-enable them one by one to identify if a particular plugin is causing the issue.

If you find which plugin is responsible, you can reach out to their support forum for better assistance.

Here are a few things to try to troubleshoot the issue:

To address potential plugin-related problems, you can rename the plugin folder to prevent WordPress from loading them. Start by locating the plugins folder within your wp-content directory and rename it to something like plugins_old. After reloading your site, if it loads successfully, this confirms that one of the plugins is causing the issue. You can then rename the folder back to plugins and systematically rename each individual plugin folder one by one to identify the problematic plugin.

If you have a backup from before the update, consider restoring it to return your site to its previously working state.

Another helpful approach is enabling Debug mode in your WordPress application. This can be done by adding a couple of definitions to your wp-config file. After making these changes and reloading the site, a debug.log file should appear in your wp-content folder. This log typically contains information related to problematic plugins or themes, which can help identify what’s causing the error on your site. For full guidance and step-by-step instructions on enabling the Debug log, you can refer to the WordPress developer documentation at: https://developer.www.ads-software.com/advanced-administration/debug/debug-wordpress/

To customize or change the button color in the Product By Category element, you have a couple of options. You can use custom CSS, edit the CSS through the theme code, or install a plugin designed for styling WooCommerce elements, such as Elementor. You might also find this forum topic useful:?Changing?ButtonColours?on?WooCommerce.

Regarding the broken Sale logo, if everything appears normal in the backend, the issue could be related to caching or a CSS conflict. I recommend clearing the cache if you’re using a caching plugin, as well as clearing your browser cache to see if that resolves the issue. Additionally, consider disabling your plugins temporarily, as one of them might be conflicting with your CSS and causing the button issue.

You can try clearing your Elementor cache to see if that resolves the issue.

1. Log in to your WordPress admin dashboard.
2. Navigate to Elementor > Tools.
3. Go to the General tab.
4. Click on the Regenerate CSS button. This will regenerate the CSS files and clear the cache related to styling.

For the best assistance, you can also reach out to Elementor’s support forum: Elementor Support Forum.

Good luck, and I hope you get this sorted out soon!

Here are some steps you can take to investigate further:

1. Check Server Error Logs: These can provide detailed insights into the issue.
2. Enable Debugging: This will also help identify any specific errors.
3. Increase PHP Memory Limit: Sometimes, a 500 error occurs due to insufficient memory, so consider increasing it.
4. Ensure Compatibility: Make sure all plugins and the active theme are compatible with your WordPress version.
5. Check File Permissions: Directories should typically be set to?755?and files to?644.

If none of these steps resolve the issue, I recommend reaching out to your hosting provider’s support team for further assistance.

Since you’ve already tried clearing caches, I think the issue might be in your .htaccess file. Sometimes after restoring backups or changing URLs, the .htaccess file can end up with conflicting redirect rules that affect how WordPress handles your URLs.

Before making any changes, be sure to create a backup copy of the current file first, just in case you need to revert it later.

You can try resetting it to the default WordPress rules: https://developer.www.ads-software.com/advanced-administration/server/web-server/httpd/

Personally, I don’t have experience using Meta Box. Perhaps you could ask in the plugin’s dedicated support forum: MetaBox Support Forum.

Alternatively, if you’re looking for a more user-friendly interface, consider using a dedicated form plugin like Gravity Forms (Dynamically Populating Drop-Down or Radio Buttons Fields) or WPForms (How to Set Dynamic Field DefaultValues in WPForms). Both of these plugins offer built-in capabilities for creating dynamic dropdowns based on previous entries.

To troubleshoot the issue, start by disabling all your plugins and then activate only the one you’re trying to update. If the problem goes away, reactivate the other plugins one by one to identify the conflicting one.

Additionally, slow performance on the plugins page may suggest a database issue. Consider optimizing your database and test afterward to see if it improves the situation.

You can also follow the guide to start debugging to see what exactly is causing the error. Here are the steps you can take: Debugging in WordPress.

You’re most welcome! ??

Hey there! First, I recommend backing up your current site state, even if it’s not functioning properly, to have a restore point in case something goes wrong.

Here’s how to restore your backup through cPanel:

Start by making a backup of your current site state (even though it’s broken) just to be safe. In cPanel, navigate to the “Backup” or “Backup Wizard” section and choose “Restore a Home Directory Backup.” Then, upload the backup file you downloaded to your desktop and follow the prompts in the restore wizard. These steps are generally applicable, but they may vary depending on your hosting provider and their cPanel customizations, so don’t hesitate to ask your provider for assistance.

If your backup includes a database export (usually a .sql file), you’ll need to restore this as well. You can do this by going to phpMyAdmin in cPanel, selecting your WordPress database, and using the Import tab to upload your .sql file. (For more details, refer to this guide.)

Once everything is restored, check your site to see if it’s functioning correctly. In the future, consider using a staging environment to test updates before applying them to your live site, as this can help prevent issues like this.

If you encounter any specific errors during the restoration process or need more detailed guidance, feel free to share them here. Good luck, and I hope your site is back up and running soon!

• This reply was modified 1 month ago by Lina Asenova.
• This reply was modified 1 month ago by Lina Asenova.

It seems like a caching issue could be the problem, especially since only your homepage is affected while other pages are working fine. To fix this, you can start by clearing all plugin caches. If you’re using any caching plugins, be sure to flush their cache as well.

If you’re using a page builder like Elementor, go to?Elementor > Tools > Regenerate CSS, and clear the plugin’s cache. Additionally, it’s a good idea to clear your browser cache or try accessing your site in incognito mode to rule out local caching issues.

If you have a CDN service like Cloudflare, make sure to clear its cache too.

It’s also possible that a plugin or theme conflict is causing this issue. To troubleshoot, try disabling all plugins and switching to one of the default themes (like Twenty Twenty-One or Twenty Twenty-Two). If the problem disappears, you can re-enable your plugins one by one to identify the source of the conflict.

Lastly, search your database for any remaining instances of the incorrect URL using a search/replace tool to ensure it’s completely removed.

If none of these steps resolve the issue, feel free to share your website URL, and I’ll take a closer look to help you troubleshoot further.

You’re most welcome! I look forward to hearing how it goes. Good luck!

Yes, just make sure that it meets Google’s eligibility requirements mentioned in my previous response. I recommend reviewing them carefully before you submit it for approval. Good luck!

One effective approach is to block bots using other meta parameters, such as the User Agent. Since the IPs are constantly changing, focusing on the User Agent allows you to identify and block requests that match specific patterns associated with these bots. This can help reduce unwanted traffic without blocking legitimate users, as many bots often use identifiable User Agents. Keep in mind, however, that blocking User Agents can be risky, as you might inadvertently block real users. Look for patterns such as very specific browser builds/versions in the User Agent strings. Common examples used by bots or crawlers include “go-http-client/1.1”. You can find detailed instructions on how to block specific User Agents in Wordfence here: https://www.wordfence.com/help/blocking/

Another helpful meta parameter to block is the Referer. The Referer header indicates the URL from which a visitor arrived at your page. You can identify potential bots by looking for unusual or suspicious URLs, such as links from spammy sites or repeated patterns from the same source. An absence of a Referer can also signal bot activity. Blocking specific Referers in your security settings can help mitigate unwanted traffic.

If you don’t have regular visitors from Ireland, blocking traffic from that region could help eliminate these unwanted requests, as you’ve noted that the IPs originate from Dublin.

Lastly, you might want to consider a hosting provider that offers a higher level of security measures to handle these issues for you. Look for a provider with built-in security features that can help protect your site from malicious traffic and automate the blocking of suspicious activity. 

There is indeed a problem, as a 404 error is visible. This type of error typically indicates that there may be an issue with how your server is handling the request, often related to your .htaccess file or server configuration. Such problems are usually caused by .htaccess files, which contain various rules and redirects that can start to contradict each other.

I recommend checking your .htaccess file to ensure there are no misconfigurations or conflicting redirects. You should remove any unnecessary rules and keep only the default .htaccess rules for WordPress. Be careful when making changes, and be sure to create a backup of the file just in case you need to revert to the original. You can find more information about configuring this file in the official WordPress documentation here: https://developer.www.ads-software.com/advanced-administration/server/web-server/httpd/

If you’re not comfortable making these changes yourself, it might be a good idea to reach out to your hosting provider for assistance. They should be able to help you troubleshoot the issue further.

NOTE: As I am not familiar with your exact web server setup, keep in mind that you might not be using Apache and .htaccess at all. For more information about your web server setup, you can again check with your host; it could be Nginx, Windows IIS, or even something else.