Hi I have a problem with chrnonoform rendering in k2 modules
you can see what is going on here on this page, basically chronoforms plugin won't render in k2_content module, though it render perfectly in component. It loads in joomla modules perfect
http://vividnight.com/joomlatest/
have been asking k2 developers about this problem and they are saying this:
we are having this conversation on twitter and you can see all the converstion @k2devs on twitter
So k2 is saying that this is chronoforms plugin problem andI'm having this problem only with chrono forms plugin, so not sure where is the problem.
I started to have this problem after I update to joomla 1.7. and to new k2 (2.5.4)
you can see what is going on here on this page, basically chronoforms plugin won't render in k2_content module, though it render perfectly in component. It loads in joomla modules perfect
http://vividnight.com/joomlatest/
have been asking k2 developers about this problem and they are saying this:
Then this plugin has hardcoded checks WHERE to render. All K2 modules use standard plugin event hooks. It's up to the plugin …of course where to render… As you can understand, if this plugin is limited to core joomla modules only, then that's stupid.
we are having this conversation on twitter and you can see all the converstion @k2devs on twitter
So k2 is saying that this is chronoforms plugin problem andI'm having this problem only with chrono forms plugin, so not sure where is the problem.
I started to have this problem after I update to joomla 1.7. and to new k2 (2.5.4)
Hi dezignas ,
I know very little about this; I can tell you that the ChronoForms plug-in in still triggered by onContentPrepare (one of those standard Joomla! hooks). Looking at Max's code it doesn't seem to quite match the examples for Joomla! 1.7 so perhaps some updating is needed. Though I don't see any changes between 1.6 and 1.7.
Bob
I know very little about this; I can tell you that the ChronoForms plug-in in still triggered by onContentPrepare (one of those standard Joomla! hooks). Looking at Max's code it doesn't seem to quite match the examples for Joomla! 1.7 so perhaps some updating is needed. Though I don't see any changes between 1.6 and 1.7.
Bob
Hi dezignas,
I'm not sure what there is to resolve :-( I don't have K2 to check anything and I don't think that Max has either. The K2 people say ChronoForms needs to use a standard hook - as far as I can see ChronoForms is using a standard hook.
If someone who has K2 can pin down the bug exactly then it may be possible to fix it.
Bob
I'm not sure what there is to resolve :-( I don't have K2 to check anything and I don't think that Max has either. The K2 people say ChronoForms needs to use a standard hook - as far as I can see ChronoForms is using a standard hook.
If someone who has K2 can pin down the bug exactly then it may be possible to fix it.
Bob
lol So this is what I'm talking about K2 people say it is chrono forms problem, Chrono forms guys say it is most likely k2 problem🙂
K2 people say it is chrono forms problem + Chrono forms guys say it is most likely k2 problem = Not working Chronoforms on K2 sites as Modules 😀
K2 people say it is chrono forms problem + Chrono forms guys say it is most likely k2 problem = Not working Chronoforms on K2 sites as Modules 😀
Hi dezignas,
I was careful not to say that it is a K2 problem - just that the problem is not clearly defined enough to know what the solution is.
Bob
Later: I've just seen your email and will take a look.
I was careful not to say that it is a K2 problem - just that the problem is not clearly defined enough to know what the solution is.
Bob
Later: I've just seen your email and will take a look.
I understand, would it be possible for you to look at my site and maybe see what is going on, I've sent you pm msg about 4 hours ago🙂
This topic is locked and no more replies can be posted.