CMS Made Simple Forums

My issues were simpler....... V2.2 couldn't save messages. I reverted to 2.1.1 and everything works as it should.

It seems to be a tradition of the module developers not to care about the modules at all

This is not my only posting where I took some time to documentate the problems of really standard modules and the result is pure ignorance of the developers.

It is not only NMS, but this module is really a kick in the ass to configurate

do you suppose we are all enlightened witchtes with crystall balls?

I am really upset.

You should try answering some of the questions here with one line explanation of problem...

Most all of the modules in forge have a page for bug tracking, feature request...

Like this one has it here, tabs for each...

http://dev.cmsmadesimple.org/projects/newsletter

Connie wrote: It seems to be a tradition of the module developers not to care about the modules at all

This is not my only posting where I took some time to documentate the problems of really standard modules and the result is pure ignorance of the developers.

It is not only NMS, but this module is really a kick in the ass to configurate

if this was my module I answered you for your bad attitude, so you talking to those who work here for free!
And not even try to be rude with me, today I am in those days that ... I do not know!!!

I begin to see here ppl very arrogant, this is not Company$ that you can  talk  like you want!

We spend many hours working here for FREE (I speak for myself), and we have  listening to this?!

If any  admin-forum want remove that my comment Fine.

THIS IS FRUSTRATING  ...

Nuno Costa

I will have to agree with Nuno here in a sense.

Connie, you are not being ignored. It is not a tradition to ignore people, they just are limited on time. Many of these developers do care about their modules but the majority of the module developers here have multiple if not dozens of modules to work on, these developers also contribute to the development of the core CMSMS package. So forgive them that they can't jump at every minor wish and feature request that every single person brings to the table. They do what they can on their own free time, but keep in mind the majority of them are already behind on PAID work so they don't have much "Free Time" to address FREE feature requests.

If any of these requests that you have are so detrimental that it must be addressed without waiting for the developer to have free time you can contact the module developer and discuss paid upgrades with them.

The tracker you are looking for would be a "Feature Request" which is on of the tabs on the Development Forge. The translations are not up to the developers. They can't quite possibly speak every language, so don't blame them. I am sure your efforts in translation would be much appreciated, especially since the German translators seem to be falling behind lately. Check out the Translations board here on the forum for more information.

Sorry,

I know about feature requests and the tracker.
Since last summer I am working with CMSimple and I am trying to figure out and documentate problems which arise whith modules

I wrote long reports already on some modules, and I posted them in the bug lists
I had success with some bug tracks and the modules were updated or finetuned

but unfortunately some of the most used modules are completely abondoned

my friends, I know that you work for free... I also do that. I developed some web applications and always was aware of user reports, problems or bugs which had to be fixed

I am not only demanding. I am giving a lot to the users as well.

But: as an example: take FCKEditor-Module

this editor-implementation has such a stupid bug in the configuration that you cannot use it all as a dummy or newbie or beginner whatever
This is posted in the forum for some months, a year, I do not know, a long time
I tested the Editor-Implementation, I wrote a list with a lot of solutions, suggestions or errors / bug to all those people which are members of that dev team
and what happened?

I was made member of that dev-team as well! Isn't that crazy???
Not one cared about my list, not one point is updated or repaired... nothing

and that is the crucial problem of CMSMS: it is a great system, but some of the modules and unfortunately the most used ones, are abondaned.

Can I tell you how much time I lost already trying to fiddle out some of these modules?
I am a human being with normal nerves and sometimes I loose them (after using all other communication medias first...)

I am still convinced that some of these developers should care about module-quality and updates OR pass that to other developers (I am not a programmer, I am a webworker and support person)

I not only one time listed the lack of quality management as one of the weak points of CMSMS, unfortunately

Connie

Me sprechen ze kiwi : )

I've got nms up and running with no probs and have VERY complicated html templates... I'm more than happy to walk you through it

Robsta

Robsta,

thanks for the offer to walk me through some problems...

that is not the point.

1) I need a documentation of the CSS-definitions of NMS and which system defines these... I do not see any documentation on that

2) I listed problems of the NMS module and I whished they were corrected, but nothing happens

that is my problem ;=)

I've read you're comments, all of them and at a high level I don't disagree.. but realistically if you've rolled your own website from scratch – ie not using the built in templates or prepackaged CSS etc... I can't really understand what the issue is with the templates and CSS...

The CSS is up to you so there's no need for documentation. You can build your own custom templates forms etc and call the class/id/element whatever you wish.... as you do when building a webpage

BUT...

CSS on the HTML newsletter template
HTML emails have to have the CSS within the email newsletters template (not through an external stylesheet)... which could be anything you wish... which means it doesn't require documenting.
BTW you can insert UDT's into the template so I just pull the stylesheet through that from the stylesheet module.

Or the admin panel's wyswig editor?
I just duplicate the styles for the newsletter in the website's main CSS file and they appear in the editor.

Or the website forms etc?
I just pop these into a separate div and call the classes etc from there... which can be anything you like as you just edit the templates.

let me know

R

did you read the start of the post?

the points I listed?

Are these points / bugs / inconveniences cleared?

I think no.

I asked also about the naming of the produced CSS IDs.
These questions are also not answered.

That is what I am claiming.
Nobody cares about my listing, but everybody treats me as a child and wants to teach me how to use CMSMS in the real way

friends, I am tired of that.

I will stop to documentate problems / bugs / shortcomings, I understand that that is not whished.