Notice: This thread is over two years old; the information may be outdated. Please consider creating a new thread if you require free support. If you have an active SiteOrigin Premium license, you can email our premium support desk at [email protected].
Does any one having the same issue with page builder not working with Timely’s All-in-One Event Calendar
Which Event plugin will work properly with this page builder can any one suggest one even plugin to use?
Hi Ramakrishna
All-in-One Event Calendar is unfortunately known to be incompatible with Page Builder. At this stage we don’t have a solution. I have seen this plugin deployed on a site running our theme but not via Page Builder, it was inserted into a regular page.
Sorry I don’t have more at this stage.
I have a conflict too with Page Builder and AI1EC, both are great plug-ins and make life easier for my clients. Do you have any idea what the conflict is? And is there any way of disabling pagebuilder on certain pages?
As an aside, have has anyone reached out from timely to SiteOrigin (or vice versa) in an effort to resolve the issues?
I have a conflict too with Page Builder and AI1EC, both are great plug-ins and make life easier for my clients. Do you have any idea what the conflict is? And is there any way of disabling pagebuilder on certain pages?
As an aside, has anyone reached out from timely to SiteOrigin (or vice versa) in an effort to resolve the issues?
Hi Rob
Under Settings > Page Builder you can disable Page Builder for post types, for example you can disable it for Posts. You also don’t need to use Page Builder on every page. To my knowledge the Event Calendar issue is only with the widget, you can still run it on a regular page in the Visual/Text tabs.
We haven’t chatted to anyone at Timely at this stage. Greg let me know that previously there was a jQuery UI conflict which he fixed. This issue being experienced now is new, we unfortunately haven’t been able to look into it.
Hi Andrew,
Thanks for your reply. I’ve managed a clunky work-around this morning with this piece of code:
inserted into the home-panels.php of Vantage.
There was another conflict with the excerpt of the events picking up content from the home page rather than from the event description so far I’ve sorted that by changing ‘the_content’ to ‘the_excerpt’ in one of ai1ec’s files. The only issue I have now is the read more link goes to the url the calendar is on rather than the event url.
I’m happy to share anything that might help resolve future issues.
Thanks Rob. Didn’t quite get through. Can you perhaps drop me mail on [email protected] and I’ll insert it here. Just don’t forget to put home-panels.php in a child theme.
Hello,
Have you found a solution for the problem ? I also have a conflict between All-in-One event calendar and IG Page Builder.
I use the calendar in the sidebar as a widget and when I’m on a page made with IG PageBuilder when I try to expand the event in order to show the event details it’s the page made with PageBuilder which is shown. I don’t have this problem if I’m on a page not made with IG PageBuilder.
It’s sad because this two plugin are really great. Have you any ideas ?
P.S : Sorry for my english I’m a french user.
Hi Alixx71
I’m afraid this thread is regarding SiteOrigin Page Builder. IG Page Builder can be found here: http://www.innogears.com/.
Hope that helps.
Hi,
Any progress with this issue?
I’m just putting up a site using Vantage Premium with Page Builder + Timely’s All-In-One-Event-Caledar -plugin.
Here’s what I’ve found:
1) The calendar works ok when using the AI1EC-shortcode on WordPress editor: http://viihdeorkesteri.fi/wp/?p=367
2) The calendar works ok when using the AI1EC-shortcode in sidebar widget and Page Builder on content area: http://viihdeorkesteri.fi/wp/?page_id=27
3) When using AI1EC-shortcode or widget inside Page Builder, it seems to create an infite loop with this content over and over again:
http://viihdeorkesteri.fi/wp/?p=363
Any idea why this is happening?
-ville-
Hi ville
Unfortunately no progress has been made here, as far as I know.
We’ve had this logged for some time. We’re a very small team, the issue has unfortunately been pushed down the queue in favour of focussing on core development. If the Timely developers were able to take a look and needed assistance, that could be offered. Sorry I don’t have better news .