Incompatible add-ons
Permalink
I’m one of probably few people who visit here who have chosen cr5 as their cms for the simple reason that it seems to provide the ability to design and develop your own site without knowing how to code. “Simply” buy the theme and add-ons you want, install them, and off you go. But of course, nothing is ever that simple.
This approach has worked fairly well over the years, but now that I have upgraded to 5.8 I'm finding that “things” seem to be more complicated. I have a block that comes bundled with my theme that just isn’t working. The package is supposedly fully compatible with 5.8. This block not only doesn’t work in its own right but, when installed, I find that about 50% of my other blocks are no longer editable. Even the core “Content” block is missing the “Cancel” and “Save” buttons, so is useless as far as editing goes.
One person suggested that problems in another add-on were the cause of the malfunction. So I have a question for the experts. Is that possible? Is it possible that one add-on can make other add-ons malfunction? If so, how is an amateur like me meant to figure out where the problem lies? What can I do if the creator of the package that I think I am having problems with suggests that the problem lies elsewhere? Do I have no choice but to hire the services of a programmer to figure it out?
This approach has worked fairly well over the years, but now that I have upgraded to 5.8 I'm finding that “things” seem to be more complicated. I have a block that comes bundled with my theme that just isn’t working. The package is supposedly fully compatible with 5.8. This block not only doesn’t work in its own right but, when installed, I find that about 50% of my other blocks are no longer editable. Even the core “Content” block is missing the “Cancel” and “Save” buttons, so is useless as far as editing goes.
One person suggested that problems in another add-on were the cause of the malfunction. So I have a question for the experts. Is that possible? Is it possible that one add-on can make other add-ons malfunction? If so, how is an amateur like me meant to figure out where the problem lies? What can I do if the creator of the package that I think I am having problems with suggests that the problem lies elsewhere? Do I have no choice but to hire the services of a programmer to figure it out?
Thanks for the idea. Seems obvious in hindsight.
I'd still be really interested in knowing the answer to the question as to whether or not packages can stuff up the functioning of other packages. If the answer is, "It's not possible", then I don't need to do what you suggest as it will be obvious where the problem lies.
I'd still be really interested in knowing the answer to the question as to whether or not packages can stuff up the functioning of other packages. If the answer is, "It's not possible", then I don't need to do what you suggest as it will be obvious where the problem lies.
> Is it possible that one add-on can make other add-ons malfunction?
Yes, absolutely. But before hiring a programmer or anything, I'd try to figure out what exactly is conflicting. Some relevant questions would be: Which concrete5 version are you running? Which add-ons are installed? Do you get a PHP error? Do you get errors in the browser / console? Have you checked the 'support' sections of the add-ons to see if there is already an issue for it? Can the problem be replicated? Have you tried asking for help via slack.concrete5.org? Do you have the same problem in other browsers? Etc.
Yes, absolutely. But before hiring a programmer or anything, I'd try to figure out what exactly is conflicting. Some relevant questions would be: Which concrete5 version are you running? Which add-ons are installed? Do you get a PHP error? Do you get errors in the browser / console? Have you checked the 'support' sections of the add-ons to see if there is already an issue for it? Can the problem be replicated? Have you tried asking for help via slack.concrete5.org? Do you have the same problem in other browsers? Etc.
From what you describe, prime suspect here would be the theme. You don't mention which theme you are using.
You can try activating Elemental as your site theme. Some page areas specific to your theme will not show, but you won't loose any content. It will reappear when (if) you reactivate your theme later.
Now run some checks for the various problems you are having with blocks. If the situation is resolved, you will know it was the theme. If not, the problem is most likely elsewhere (but could still be theme package related).
Re- activating your theme will now show the areas that disappeared.
If you end up changing theme, you can drag content in the areas that will disappear into the main area, swap themes, then drag them back out to areas of the new theme.
You can try activating Elemental as your site theme. Some page areas specific to your theme will not show, but you won't loose any content. It will reappear when (if) you reactivate your theme later.
Now run some checks for the various problems you are having with blocks. If the situation is resolved, you will know it was the theme. If not, the problem is most likely elsewhere (but could still be theme package related).
Re- activating your theme will now show the areas that disappeared.
If you end up changing theme, you can drag content in the areas that will disappear into the main area, swap themes, then drag them back out to areas of the new theme.
Maybe if we knew what add-on we're talking about we could give a clear answer?
It's the "Back to Top" block bundled with Fundamental theme. But all is now well (as explained below.)
Thank you to everybody for your answers. I found every message very helpful. Following ideas presented here I was able to verify which block was causing the problem. (And yes, JohntheFish, it was associated with the theme.) The theme creator then graciously rewrote whatever needed rewriting in the block and all now seems well.
The Concrete5 community is terrific!
The Concrete5 community is terrific!
If you choose to do this, make sure you have Pretty URLs and Caching turned off for the testing and reverting.