You’ve not provided any real data that convinces me Redux is the issue. If you believe there is an incompatibility with the theme, you will need to contact the theme’s author about it. Why? We do not have access to the theme you are using. We can do no testing. It’s also not our code to maintain. Redux is a developer’s tool, not a consumer’s one, which means typically, we do not support theme users for the aforementioned reason.
Redux often takes the blame for everything that goes wrong. Read some posts in this forum, and you’ll see theme and what I’m about to say now: Redux is an options framework. It creates the theme’s options panel. The theme author then takes the results from the panels input and crafts their code around them. So when you disable Redux, all the code the runs based on the options you choice no longer does. Any issues in that code suddenly disappear and the theme appears to work again. Redux gets blamed, and I have to type this explanation out again. Only the theme’s author can debug their theme and determine the cause. If they find an incompatibility with Redux, they need to contact us with the supporting data and we’ll work with them as only they can provide us with a copy of their theme.
If you have error data that refers to Redux from your PHP logs or in the browser’s console log, I can take a look at that, but we cannot debug theme or server issues.
You are saying that there is no bug, that there will be a problem with the theme. In addition, you said you could not test it. Instead of investigating where such a problem would originate from and helping us, you constantly reject incoming requests.
Let me briefly tell you why the problem is caused by you.
The plugin is constantly fed from external sources. For example; https://cdn.jsdelivr.net/gh/devicons/[email protected]/devicon.min.css
During these external connections, performance issues arise. Here is a sample error image; https://drive.google.com/file/d/18WaisGzag2t5I-DRbOUAQnNl6jPfLBvQ/view?usp=drive_link
A timed out error is received when trying to connect to the icon set. When the plugin is disabled, connections can be made without any problems. However, when it is activated, performance problems arise that we cannot determine exactly where they originate from.
This is not due to incompatibility between the theme and the plugin, but because of the problem the Redux plugin has when connecting to external resources.
You’re running the demo mode? Turn it off. If you are a theme user, you don’t need to run the demo. It’s for developers.
Unfortunately, I keep having the same problem when I close it. Maybe I shouldn’t have opened it at all. I uninstalled and reinstalled the plugin, but the same problem persists. I tried reinstalling under another domain and the same problem persists. We need to come up with a different solution. But I don’t know how to proceed.
Is there any reason you won’t contact the theme author and have them evaluate it? It is their theme after all, and I do not have access to their theme. We also have no control over how theme authors integrate Redux into their theme. There could very well be a theme issue at play here, but for reasons I don’t understand, you want to blame Redux, all because you disabled it and everything worked again. I’ve already explained why that is. Now it’s time to bring the other half of the equation into it: The people who wrote them theme. There is nothing else I can do. If the theme author discovers and issue and has data on how and why Redux is the issue, they need to report it to us as only they can provide a copy of their theme for us to look at. Otherwise, I can’t fix what I can’t break.
I might also look into why cURL timeouts are occurring on your server when the CDN is active and working. It could be caused by a firewall or security plugins, if you have them (which I do not know because that information wasn’t provided. Just a demand to fix something that likely isn’t our fault). They can also be caused by outdated server software or inadequate server resources.
