[SOLVED] Formbuilder CMSMailer module requirement

[wmdvanzyl]

I couldn't install Formbuilder using the built-in module manager due to an error, so i used the XML process instead. It reports a missing dependency, CMSMailer.

I might be wrong, but i understood that CMSMailer is no longer part of CMSMS2 (mailer functions are now core?), so Formbuilder probably shouldn't have this requirement.

Am i missing something? I'm sure i must be, since lots of people use this.

[velden]

http://forum.cmsmadesimple.org/viewtopi ... 72#p325072

[chandra]

Maybe you should post a feature request.

A switch between 1.x and 2.x is easy to realize ...

[Jo Morg]

It reports a missing dependency, CMSMailer.

I might be wrong, but i understood that CMSMailer is no longer part of CMSMS2 (mailer functions are now core?), so Formbuilder probably shouldn't have this requirement.

That is as designed. As the link that velden posted shows, it is a requirement as long as FB supports both branches of CMSMS. And FB is not the only module doing this, IIRC FEU does too.

As a side note: in CMSMS 2+ CMSMailer is a wrapper of the core functionality, and is there specifically for this purpose, so there is nothing odd about this situation. It will most likely be removed after support for CMSMS 1.x branch ends and most modules are already compatible with CMSMS 2+ API and NOT needing to support both branches of CMSMS.

[wmdvanzyl]

I think what adds to the confusion is the fact that CMSMailer is not available using the ModuleManager. So i have to downlaod it manually and install it using the XML process. None of which is a problem, but it is a little confusing, especially for a new user (i would imagine).

[Jo Morg]

I think what adds to the confusion is the fact that CMSMailer is not available using the ModuleManager. So i have to downlaod it manually and install it using the XML process. None of which is a problem, but it is a little confusing, especially for a new user (i would imagine).

THE CMSMailer that ships with CMSMS 2+, although a wrapper, is a full fledged module on it's own. There is no need to download ANY other version of CMSMailer whatsoever. You just need to install it (it comes with CMSMS but is not installed by default). There is nothing confusing about this.
From Introducing CMSMS 2.0:

Though a CMSMailer module exists as part of the core, it is now just a stub module without an interface. Its only purpose is for backwards compatibility with older code, and as such it is not installed by default for new installs.

It's perfectly clear IMO.

[wmdvanzyl]

THE CMSMailer that ships with CMSMS 2+, although a wrapper, is a full fledged module on it's own. There is no need to download ANY other version of CMSMailer whatsoever. You just need to install it (it comes with CMSMS but is not installed by default). There is nothing confusing about this.

I obviously respect your opinion and i don't mean to be demanding in any way. I am just saying that from my perspective, it was a bit confusing. I needed to come here to the forums to understand what was happening. Look at it from my perspective:

1.) Go to Module Manager and try to install Formbuilder. It gives an error that i don't understand.
2.) Downlaod Formbuilder and import via XML. Get missing dependency message for CMSMailer.
3.) Search for CMSMailer and/or alphabetical listing - CMSMailer not found
4.) Downlaod CMSMailer from the forge and import via XML. Install, but get warning about it being deprecated.
5.) Install Formbuilder - Done!

I think that process is confusing for a new user. If you don't understand the dependency situation, then installing a deprecated module downloaded from the forge isn't obvious.

Perhaps i am going about this the wrong way? What should it look like when someone does a clean 2.0 install and tries to add FormBuilder?

[Jo Morg]

Look at it from my perspective:

1.) Go to Module Manager and try to install Formbuilder. It gives an error that i don't understand.

That's were you stop and come here for help with a full description of the error and when did it happen...

Don't get me wrong: I understand that you had a problem and that you needed to have it solved. It's just that since the current FB dev team started working on FormBuilder to make it ready for CMSMS 2+ (we started when it was on beta stages) we have installed it a few hundred times already and although it is a complex module, working on a complex CMSMS (in terms of how they work under the hood) and it was close to impossible to test every little thing, we did our best to prevent issues.

Of the 5 steps you describe, I have never seen 1, thus never had to use 2 and although there was a missing dependency (CMSMailer) it was listed there, in red, so I just installed it without having to go to 4 and missed 5 because FB was already installed on step 1.

I just used 2 steps and was ready to go. And these steps weren't far off of usual installations of modules.

So, I reiterate: you should have stopped at the 1st error, take notes and asked for help. Given enough data we might have been able to replicate the error or give you clues on what might have gone wrong on your particular case.

[wmdvanzyl]

Look at it from my perspective:

1.) Go to Module Manager and try to install Formbuilder. It gives an error that i don't understand.

That's were you stop and come here for help with a full description of the error and when did it happen...

Don't get me wrong: I understand that you had a problem and that you needed to have it solved. It's just that since the current FB dev team started working on FormBuilder to make it ready for CMSMS 2+ (we started when it was on beta stages) we have installed it a few hundred times already and although it is a complex module, working on a complex CMSMS (in terms of how they work under the hood) and it was close to impossible to test every little thing, we did our best to prevent issues.

Of the 5 steps you describe, I have never seen 1, thus never had to use 2 and although there was a missing dependency (CMSMailer) it was listed there, in red, so I just installed it without having to go to 4 and missed 5 because FB was already installed on step 1.

I just used 2 steps and was ready to go. And these steps weren't far off of usual installations of modules.

So, I reiterate: you should have stopped at the 1st error, take notes and asked for help. Given enough data we might have been able to replicate the error or give you clues on what might have gone wrong on your particular case.

Thanks for taking the time to respond. I am grateful for all the work work that goes into modules such as this.

The reason i don't just jump on here on ask for help after step 1 is my innate desire to try and solve the problem myself.

As developers (speaking from past experience) it happens quite often that "it works on the developer's machine".

I didn't mean any insult or offense, i'm just trying to expose a few niggles that new/inexperienced users might experience. There are so many CMS'es to choose from and i wouldn't want the community losing members over seemingly issues such as basic modules with missing dependencies. As you mentioned, it's not that simple and i understand that; and i realise there is no better solution at present.

Thanks again! Installing CMSMailer using XML solved my issue.