Watchman

Does the new version support the watchman plugin which is included in version 3.2?

I installed version 4 but have not been able to find the watchman plugin anywhere.

Hi moleculezz ,

I haven't re-written the Watchman plug-in as a CFv4 action. I expect I can do if there is some interest. The User Group part is now built in to ChronoForms as the Authenticator action in the Security group.

Bob

Well I'm interested 😀

The reason why I ask is that I have a dilemma.

Since IE9 came to be, one of my forms doesn't work (which is using the calendar). In IE9 the calendar button is not displayed. This again is because MooTools 1.12 does not work in IE9. So I have to enable the Joomla MooTools upgrade plugin, but then the calendar still doesn't work because the calendar is not compatible with MooTools 1.2.5.

Then I thought I might have to upgrade Chronoforms also, but I am also using the Watchman plugin and it doesn't seem to be included in Chronoforms v4.
Also if I upgrade to Chronoforms v4, I would have to rewrite some custom js I made especially for the calendar since Chronoforms v4 uses a different calendar script.

So now I'm kinda stuck.

Is there any advice as to how I could go by solving this issue I'm having?

Hi moleculezz,

Short term - try forcing IE9 to run in IE8 mode and see if that fixes the the script problem. See the code in this post

Longer term - CFv4 is probably the way to go.

Bob

I would do CFv4, but without the Watchman plugin don't see how I will be able to do that.

In any case, I have found an alternate solution, haven't completely tested it yet, but I wen't ahead and made the aeron calendar to be compatible with MooTools 1.2.5.

So the calendar works with MooTools 1.2.5, but now I get other issues with chronoforms.
Does Chronoforms V3 not work with the mootools upgrade plugin?

Hi moleculezz,

No it doesn’t. ChronoForms v3 requires MooTools 1.12; ChronoForms v4 requires MooTools v2.5 or v3

Bob

Hi moleculezz,

Short term - try forcing IE9 to run in IE8 mode and see if that fixes the the script problem. See the code in this post

Bob

I'm confused, in that post it seems that a few people were using v3 with the mootools plugin and got it working. Yet from what you are saying it is not?

Also I don't see where I can add the custom code. Should I just add it at the top of the "Form HTML"

Hi Moleculezz,

I did create a hacked version of ChronoForms v3 where the front-end only could be run with the MooTools plug-in enabled; and a hacked version of the plug-in to go with it that loaded MooTools 2.5 in the front-end and MooToosl 1.12 in the admin area.

Bob

I understand.

So what should I do?

I can't upgrade to V4 currently because of the watchman plugin, and also I need a quick fix right now since the form is already live and I need to fix it asap.

I tried to add the piece of code in the "HTML Form" but that didn't work. Do I need the hacked version to get it running?

Hi moleculezz,

I don't have a quick fix for you and I don't have time to rewrite the Watchman plug-in before I go on holiday in an hour or so.

You might be able to add code to the form to do whatever it is you are using the Watchman for.

The simplest answer is still to use your old form and force IE9 to run in IE8 compatibility mode.

Bob

Yes, I think the simplest thing is to use old form and force IE8 compatibility, but it's not working.

Can you tell me where exactly I have to put the code? I put it on top of the "HTML Form", but it's not working.

Ok it works! For some reason it wasn't working on the local copy I had running.

Thanks for the help GreyHead.

By any chance, was the watchman plugin implemented as an action?

Yes it was, Bob should have the latest up to date file though, try to send him an email or PM for the file or check this one:

http://greyhead.net/how-to-docs/cfv4-watchman-gh-action

Regards,
Max

Hi moleculezz,

I'm pretty certain that is the most recent version.

Bob

Awesome... thanks guys. I can now make the upgrade to V4 and bypass the IE9 hack.

Thanks again!