If you’ve ever run into a white screen while trying to edit a post or page in WordPress, you know how frustrating it can be — especially when it happens on a live site. I recently faced this exact issue on a WordPress website hosted on Cloudways, and here’s how I identified and fixed it, I am an expert in WordPress Customization so this was easy to solve with a little bit of help from internet.
The Problem
One day, I logged into the WordPress admin area of a live website and tried to edit a post. But instead of loading the content editor, the screen was completely blank — no errors, just a white screen. This issue persisted across multiple posts and pages, making content management impossible.
Initial Troubleshooting
To avoid disrupting the live environment while investigating the problem, I cloned the site to a staging environment on Cloudways. To my surprise, the white screen issue didn’t occur on the staging site.
At this point, I knew the issue wasn’t related to the WordPress core, the theme, or the plugins, because the staging site was an exact replica of the live one. That led me to believe the problem had to be something external.
The Clue
Digging deeper, I checked the Cloudways error log and saw a message that hinted at the issue: “cache full”
That was my first real lead. I tried clearing the cache using the WordPress caching plugin installed on the site, but it didn’t solve the problem.
The Real Fix
Then I remembered a key difference between the two environments: The live site was using Cloudflare, while the staging site was not.
So I went into the Cloudflare dashboard and purged the cache.
Immediately after clearing the Cloudflare cache, the white screen issue disappeared on the live site. The editor pages began loading normally again, and everything was back to business as usual.
Takeaway
If you’re seeing a blank screen when editing posts or pages in WordPress and everything seems fine otherwise, Cloudflare cache could be the culprit — especially if your staging site works but your live site doesn’t.
If you’ve ever tried to add text or elements under an image using the King Composer website builder and faced issues, you’re not alone.
How to Fix King Composer Plugin Issues with Object Cache Pro
I recently encountered a similar problem where the text blocks and images wouldn’t save correctly after updating the page. In this blog post, I’ll share how I identified the issue and resolved it, and provide insights for anyone facing similar challenges. Jump to the bottom to see the video and steps.
The Problem: Elements Not Saving Correctly
I was trying to add a text block under an image using the King Composer builder. After saving and updating the page, I expected to see an empty block, followed by an image and a text block labeled “sample text.” However, after refreshing the page, the text block wasn’t visible. This missing content was a clear indication of a bug within the builder.
Cause of the Issue: Object Cache Pro Plugin Conflict
After some investigation, I discovered the problem was caused by a caching plugin called “Object Cache Pro.” This plugin, designed to handle website caching, was interfering with the King Composer builder, preventing new elements from saving correctly. Caching plugins can sometimes cause conflicts with page builders, especially when these builders rely on dynamic content updates.
Solution: Disabling the Caching Plugin
To resolve this issue, I temporarily deactivated the Object Cache Pro plugin. After doing this, I could add, edit, and update elements within King Composer without any issues. Once I confirmed everything was working correctly, I saved the changes and reloaded the page.
Here’s a step-by-step guide on how you can fix this issue:
Deactivate Object Cache Pro Plugin: Go to your WordPress dashboard, navigate to the plugins section, and deactivate the Object Cache Pro plugin. This should allow you to make changes without interference.
Make the Necessary Changes: Add or edit the elements on your page using King Composer.
Save and Update the Page: Once your edits are complete, update the page and check if the changes are visible on the frontend.
Reactivate the Caching Plugin (Optional): If you need to, you can reactivate the Object Cache Pro plugin, but keep an eye on any conflicts that may arise. Consider switching to a different caching solution if the issue persists.
Why the Problem Exists: Plugin Abandonment
The King Composer plugin has not been updated in over three years, which can lead to compatibility issues with other plugins, especially caching solutions. When plugins are not actively maintained, they may not work seamlessly with newer versions of WordPress or other updated plugins. This is frustrating, especially when a once-reliable tool starts causing problems.
Conclusion: Keep Plugins Updated and Report Issues
If you’re a developer or website owner using King Composer, be aware of potential plugin conflicts, particularly with caching plugins. If you face similar issues, try disabling your caching solution temporarily to see if it resolves the problem. And, if possible, report the issue to the plugin developers to encourage them to release updates.
Hopefully, King Composer developers will address these compatibility issues in future updates. For now, if you encounter problems, follow the steps outlined above to troubleshoot and fix them.
Feel free to share your experiences or additional troubleshooting tips in the comments. Let’s help each other navigate these technical challenges!
In today’s tutorial, I’ll walk you through the process of dynamically showing different languages on a WordPress website using the Visual Composer plugin, alongside the Polylang translation plugin. This setup will allow your website to display content in various languages based on user selection. Let’s dive into the details.
Introduction to Visual Composer and Polylang
Visual Composer is a drag-and-drop page builder plugin for WordPress, similar to Elementor, that allows you to create visually appealing pages without writing code. However, if you are using Polylang, a plugin designed to translate your website into multiple languages, it might not directly support dynamic text changes inside Visual Composer. But don’t worry; by using some custom code and shortcodes, you can integrate Polylang to work seamlessly with Visual Composer.
The Problem and the Solution
When I was searching for a solution to dynamically change text inside Visual Composer based on the user’s language preference, I realized there wasn’t a direct method available from the Polylang plugin. To overcome this limitation, I created a shortcode that responds when a user switches between languages. This shortcode dynamically displays the appropriate text in the selected language on the page. Below is a screenshot from my website, where we have different languages to select from in the header menu.
Step-by-Step Guide
Here’s how you can achieve this functionality:
1. Create a Custom Function
Start by creating a custom function in your functions.php file, which is part of your WordPress theme. This function will allow us to generate dynamic content in multiple languages.
For example, let’s say we want to dynamically display the “About Us” section in different languages. Here’s a sample PHP code that you can copy-paste in your functions.php file:
<?php
function footer_about_us() {
if(pll_current_language() == 'en') {
echo '<div class="footer-footeraboutus">
This is an english line. jaksd ashdajs dha jshdajs hd
</div>';
} else if(pll_current_language() == 'fr') {
echo '<div class="footer-footeraboutus">
This is fr line. sadasdasdajksdh asjdh ajs hdjashd
</div>';
} else if(pll_current_language() == 'de') {
echo '<div class="footer-footeraboutus">
This is de line. jhsda jashdjahsd jashdaj kshd
</div>';
}
}
add_shortcode('footeraboutus', 'footer_about_us');
// [footeraboutus]
?>
In this code:
pll_current_language() is a Polylang function that detects the current language.
Based on the current language, it returns the appropriate text (in this case, either English or French).
2. Add a Shortcode
Once you have your custom function, the next step is to register it as a shortcode in WordPress. Shortcodes allow you to insert dynamic content into posts and pages easily.
Now, you can use the shortcode [footeraboutus] anywhere on your website, including Visual Composer elements, and it will display the correct content based on the selected language.
3. Insert Shortcode in Visual Composer
After creating the shortcode, you need to insert it into your Visual Composer page. To do this:
Go to the page you want to edit using Visual Composer.
Click on the element where you want to display the dynamic text.
Paste the shortcode [footeraboutus] inside the element.
Once the page is updated, the content in this section will dynamically change based on the language selected by the user.
Final Steps
After setting up the shortcode and inserting it into the page, all that’s left is to test it. When a user selects a different language (for example, English or French) from the Polylang language switcher, the corresponding content will be displayed automatically.
This method allows you to:
Dynamically display different languages on your website pages.
Easily manage multilingual content using Polylang and shortcodes.
Conclusion
With this approach, you can integrate the Polylang translation plugin with Visual Composer to create a seamless, multilingual WordPress website. The key lies in creating custom functions and shortcodes that respond to language changes dynamically. Whether you’re building an “About Us” section or any other content block, this method will ensure your users get the right content in their preferred language.
If you have any questions, feel free to leave them in the comments below. Don’t forget to like and share this article if you found it helpful!
