wdberatung wrote:
A search for this errormessage brings 2 pages results! ;=)
So this is a common problem and not all who asked, got answer or help.
However it is not a common error of the core of CMSms but of certain modules/plugins developed by 3rd party developers. So please talk to the developers of the modules/plugins that cause this error.
And again you do not give any info about what modules or plugins you're talking about.
Saying it is the "published CMSMS modules or plugins" doesn't mean anything since there are loads of modules or plugins "published" in the forge that are maintained by 3rd party developers and might be just created for one particular reason or even for one certain CMSms version.
You cannot expect the core developers to test all 3rd party modules before "publishing" them. This is up to the module/plugin developer itself. If i create a module/plugin that does not work it is my fault not the dev teams.
It would be nice to have such a quality ensurance to make sure only proper working modules are in the download section.
Would you like to do that job?
But i agree, it would be nice to see in the download section what CMSms versions a module/plugin is compatible to before downloading it.
As jmcgin51 said:
The ModuleManager should only show/install modules that should work with your CMSms version.
However even this is no warranty.
Anyway... are you talking about core modules?
(modules that are officially maintained by the CMSms development team and comes with the default CMSms installation)
I don't have that errors so i guess it must be some weird settings of your server or you use modules/plugins that are not compatible with CMSms 1.7.1 anymore.
So please, just give some info about what module/plugin exactly is causing this issue.
Enable debug mode to (maybe) see some more messages/notices/warnings etc.
Otherwise no one can figure out what is going on.