After digging a bit deeper into your profile I do see what you mean. It is problematic indeed. How active is really the development of SuiteCRM really or is salesagility putting the money and efforts somewhere else?
That Is just ridiculous and sounds insane. Why have they done that? Doesn’t make sense to me. Using one and the same makes logical sense, right?
It’s a big they. Many people, over many years of developments. Some of the code in SuiteCRM is quite excellent, some of it sucks, and TinyMCE integration I would say is one of those nasty areas. Got off to a bad start, then whenever people added it in one more screen they would avoid the mess by starting over, thus creating a bigger mess.
My ongoing list of Places where TinyMCE is used:
email templates edit view
user profile, email settings, signatures
emails module, compose
PDF Templates module
KB module
campaigns wizard, inline when editing the templates
Cases module, threaded updates
several Description fields in several modules
There are probably more that I haven’t discovered yet.
The approach I started to take is to
Make the user-configured editor a proper SugarField, to ensure that the entanglement with the View code is done properly, not with specific hacks to every screen (usually quite ugly, since they require both HTML and JS)
Make the TinyMCE configuration independent of the code, and make it extensible by users
I’ve done this for a couple of templates screens, but I won’t call my approach “successful” until I’ve implemented it in a few more screens (I might get stuck and find out it’s not a workable solution).
I don’t really know. I see that GitHub is much less active than it should be, since January. I know that Covid didn’t help at all. I know that there is serious money and efforts going into Suite8, which is mostly UI work.
My personal approach is this: instead of just complaining that SA should do more, I try to be thankful for what they do. It’s a lot. But I do feel the pain of the slowdown in the project, and I think much more needs to go into Suite8 besides UI work.
That’s why I launched my SponsorWare campaign, idealistically thinking that the Community could back me (many small sponsorships providing a nice added up value) so I could work on those things that I believe are high among people’s priorities. Robustness, eliminating current pain points, Email, etc.
I want the community to hire me as the extra developer that SuiteCRM needs
Thanks a lot @pgr for explaining this as this makes me understand things more.
Well for users like me it more also a question if you should base your company on a system that is slowing down or not. Can you trust its future development and stability etc? It cost money to change system and it cost money to start using a system etc. So you want to be certain as company owner. I do like your idea though and I hope I can contribute and buy your addons because they do look really useful and cool.
As a startup like mine you need some check boxes ticked off first before you can do something like that though.
With regards to the tinymce mess. How about starting a local community crowdfunding to fund a cleanup of that “crap code”?
There must be interest by all SuiteCRM users e.g. the companies to make this be fixed so it is more user friendly both for the admins and for the end-users?
Hi @pgr
Well I mean more like an official “donate” thread or something that announcees this to the whole SuiteCRM community. Heck it even could be the the Patreon platform, for example. Revive Adserver (former Open X community edition) uses Patreon too:
Just a quick question. I had not success with trying to add the hyberlink button etc. I did however mange to enable the toolbar menu but changing the value from “false” to “true” and that sort of works because there is a hyberlink feature in that.
But I do also really need to enable the html source button too so i can copy/paste some code snippets into my emails. (Some marketing stuff)
Do you have any idea on how to do that?
Also do you have any idea why the system refused to add the other button? If you have have any idea/suggestion what it could be that could lead me in the right direct it would be greatly appreciated.
@PowerQuest
I don’t understand, where do you have a problem? I added the buttons in 3 minuets.
I don’t understand, where do you have a problem? I added the buttons in 3 minutes. Look at my changing in file ‘modules/Emails/include/ComposeView/EmailsComposeView.js’
I did exactly that and hmm nothing happened on my side. But to be fair I had not turned on the “developer mode” when i did it and uploaded the changes through ftp.
I did try to add some other plugins too by looking into the tinymce plugin folder/plugin code. That didn’t work well either. But I might done something wrong of course when testing with the others.
That body text box is filling the whole window and outside too as you can see too. Never seen that before. The upgrade itself went smoothly without any errors was reported.
In Brave dev tools it is reported that Tiny fails to load:
So what do I need to do in the .htaccess file to resolve this so the email popup (in leads) loads normally?
I see that in the dev tools (Please see the screenshot above) it refers to the file https://mydomain-name.work/jquery.qtip.min.js which is failing to load with a 404.
But there is no such file in the root folder. I also downloaded the newest installation package (Just to check), and that file is missing there too.
They way I read it there is no real solution to this bug. Rolling back is something I could do through our backup systems of our server but that would also mean losing production data. So I’m stuck between a rock and a hard place.
@p.konetskiy If it derives from the .htaccess file… is there big differences in the versions. Could it work with just replacing the newest version and use the old one instead?
@PowerQuest
The file .htaccess is part of config web-server (apache, nginx or ect.). It is’n influence on working SuiteCRM directly.There is rule access to directories and files SuiteCRM only.
You can change file but new version can solve problems with unauthorized access to directories and files SuiteCRM. I thick that the better varint to fix the bug into new version.
Right thanks. I do understand the functions of .htaccess file and why you should normally not tamper with it…
But this bug is just so annoying and is limiting to your ability to work properly in the system so that is why I considered to do something with the .htaccess file.
I need to just email through the normal MS Outlook as worst case scenario if salesagility doesn’t come up with a fix ASAP. But then I will lose the connection relationship in lead records and emails obviously.