I'm trying to use Chronoforms in a module position via Eike's Place Here (a.k.a. Content Display Module), per the FAQ 43 recommendation. Everything works beautifully, except for one terrible side effect...
The site template I'm using includes collapsible menu trees. When the PH module that includes the CF article page is published, ALL menu trees expand. This happens only for Place Here modules that include pages with {chronoforms} tags.
I realize there are many factors involved here (template > page > module > CF plugin > CF component); however, something in Chronoforms seems to be the trigger. CF works fine on article pages. PH works fine, except with Chronoforms, so I'm hoping you can suggest a solution.
BTW, I've tried and failed to get CF to work at all with Ultimate Content display, Flex Content, Wrapper, Global News, or any other show-page/category-in-module-position module. Place Here seems to be the only module that doesn't choke on CF's plugin/include tag, but the consequent menu problem is killing me.
Here's hoping you can help. I just want to give my community some easy ways to interact with the site without leaving main content pages. Doesn't seem like it should be so hard. Please help.😟
Thanks. Cass
The site template I'm using includes collapsible menu trees. When the PH module that includes the CF article page is published, ALL menu trees expand. This happens only for Place Here modules that include pages with {chronoforms} tags.
I realize there are many factors involved here (template > page > module > CF plugin > CF component); however, something in Chronoforms seems to be the trigger. CF works fine on article pages. PH works fine, except with Chronoforms, so I'm hoping you can suggest a solution.
BTW, I've tried and failed to get CF to work at all with Ultimate Content display, Flex Content, Wrapper, Global News, or any other show-page/category-in-module-position module. Place Here seems to be the only module that doesn't choke on CF's plugin/include tag, but the consequent menu problem is killing me.
Here's hoping you can help. I just want to give my community some easy ways to interact with the site without leaving main content pages. Doesn't seem like it should be so hard. Please help.😟
Thanks. Cass
Hi Cass,
well, I made our own modules but still didn't add them to the downloads, check this post :
http://www.chronoengine.com/forums/index.php?option=com_chronoforums&cont=posts&f=2&t=10908&p=12351&hilit=laurel+module#p12351
Cheers
Max
well, I made our own modules but still didn't add them to the downloads, check this post :
http://www.chronoengine.com/forums/index.php?option=com_chronoforums&cont=posts&f=2&t=10908&p=12351&hilit=laurel+module#p12351
Cheers
Max
Hi, Max.
Looks like your recommendation has lots of potential, except....
I use Community Builder, and according to my own experience and the thread below CF V3 won't work with Community Builder.
http://www.chronoengine.com/forums.html?cont=posts&f=2&t=10806&p=11669&hilit=failed+opening+%27%2Fcomponents%2Fcom_comprofiler%2F#p11669
CF 2.5 worked fine with Community Builder, but that still leaves the original issue of publishing CF in module positions.
So, I guess the lingering question is: Is there either a V2.5 fix for publishing in module positions OR is there a V3.0 fix for using CF with Community Builder? Either solution would work, I think.
Thanks!
Diorist
Looks like your recommendation has lots of potential, except....
I use Community Builder, and according to my own experience and the thread below CF V3 won't work with Community Builder.
http://www.chronoengine.com/forums.html?cont=posts&f=2&t=10806&p=11669&hilit=failed+opening+%27%2Fcomponents%2Fcom_comprofiler%2F#p11669
CF 2.5 worked fine with Community Builder, but that still leaves the original issue of publishing CF in module positions.
So, I guess the lingering question is: Is there either a V2.5 fix for publishing in module positions OR is there a V3.0 fix for using CF with Community Builder? Either solution would work, I think.
Thanks!
Diorist
Hi Diorist,
please backup your forms and uninstall BETA 2, search the forums for BETA 2.1 and get that package and install it and let me know if the same issue still happens.
Regards
Max
please backup your forms and uninstall BETA 2, search the forums for BETA 2.1 and get that package and install it and let me know if the same issue still happens.
Regards
Max
Max, YOU are a magic man.
CF BETA 2.1 not only resolves the Community Builder issue, but it fixes the PH/menu problem as well.
I've always thought that Joomla, as a community-oriented CMS, made it way too hard to get form-based interactions with the community. With CF 2.1, you've changed all that. It opens so many doors.
Thank you. Thank you. Thank you.
Diorist
CF BETA 2.1 not only resolves the Community Builder issue, but it fixes the PH/menu problem as well.
I've always thought that Joomla, as a community-oriented CMS, made it way too hard to get form-based interactions with the community. With CF 2.1, you've changed all that. It opens so many doors.
Thank you. Thank you. Thank you.
Diorist
Thanks so much Diorist, anyway I advise you to get the stable release of V3.0 coming out soon, no extra features but many issues fixed and current code enhanced.
Regards
Max
Regards
Max
This topic is locked and no more replies can be posted.
