Any updates on integrating SC projects with major CMS systems (WP, Joomla, Drupal) ? I am interested to at least get SC Security modules integrate with those CMS. I really do not understand wht NETMAKE keeps ignorring this for so many years. It should be their priority and would bring them lots of new customers. Using wrappers in Joomla (for example) is causing some unexpected results. It seems to be a tiny bit easier in WP, because by default WP does not have a security database/profile/user base etc. but still integration sucks.
I wonder if anybody has done anything advanced with any of thses CMS platforms ?
Yes, It is very necessary.
Full integration in a CMS is a major task. I doubt if SC would do that. Wrappers do work fine, but it depends on what you want/need. It is fairly easy to integrate logon by accessing the database of the CMS yourself. Then you can create some kind of single login. I highly discourage creating WP, Joomla or other CMS plugins using Scriptcase. Way too much overhead. As most CMS uses bootstrap for layout and SC is not fully responsive you might encounter issues with your layout.
I know I can use iFrames, but the main goal is to unify the CMS userbase and permissions with SC App premissions.
I was thinking at some point about mergins jusers table and sc_users into one (for Joomla site). I could do this but still unsure how to merge the prmissions tables so CMS and SC can use their respective counterparts.
@aklass - I have been wrestling with this with WordPress.
The not-so-short answer is:
If you want to use WP to manage the security/logins etc then you need to use iframes on WP pages/posts etc. Any folders/apps etc deployed outside of WP managed pages/posts are just not seen by WP or any of its plugins (including membership plugins).
What I have done is deployed the project either under the WP site’s htdocs (or under a separate subdomain of that site) so it is accessible externally. Regardless, WP has no clue it’s there. I have then also deployed the SC project’s database to the server’s main MySQL instance. That MySQL instance hosts the backend DBs for a number of different WP sites on that server, and now also has the backend DB for the SC project there too. This means there only needs to be a WP page/post/menu (whatever) that points to the SC initial app, and that app then simply uses SC’s own security module.
The missing piece - which is what you are asking about (I think) is using/syncing with, say, WP’s user details with the SC module.
The only potentially beneficial thing you might consider doing with custom code on the WP side is to intercept any new user registrations (or updates) there and update the relevant SC security tables with that information so there is a matching credential in SC security. Depending on the WP page that launches to the SC app it may not be required for the user to login on WP, but once they get to the SC project, they would login there (via the SC security module credentials which will match the one they set up on WP).
If you did that, you would then also need to consider if changes should be bi-directional. Personally, in that scenario I would make WP the single-source of truth and changes from WP sync to SC, but not the other way (making sure it’s not easy/possible) for users to update their creds in SC. Of course, if it needed to be bi-directional then you would need code on SC’s side too.
At some point I may consider developing a WP plugin to manage all that - but it wouldn’t be any time soon. Be nice if the SC folks considered that…
Adz
I agree that it is convenient for WP users. I think SC should focus on SC, not integration with 3rd parties. It would mean that SC needs to keep their product updated against WP updates. Costly resources that could have been used to fix issues. WP is a (very) popular CMS, but why make a commercial product dependent on an open-source project? Especially for only a limited group of users? Commercially, that doesn’t make sense. I would not recommend creating WP plugins in SC.
1 Like
Hi Albert. I totally get your point.
However, in the case of WP many, many third-party services build a plugin to help WP integrate because it is so popular. And, yes, it also isn’t those other companies’ core offering or responsibility to do this. Of those that do, most offer it as a lost leader (i.e. as a customer service thing) that may well gain them more customers (and 99% of those companies are not open-source either).
I’m also not saying that SC need to do this - just that it would be nice (and I suspect, no doubt, just wishful thinking) 
Albert - you’re wrong on that one.
Why they should integrate SC with CMS ?
Simply because there is still not good, fast tool to build CMS apps. There are few competitors appearing on the market, though.
Another reason is that it woould bring NETMAKE huge amount of costomers.
All they need to do is to build someting like jSCRIPTCASE (which was excellent product for Joomla) but got discontinued. I know this software is for same (I spoke with the developer). The reason they stopped development was because they simply did not get enough sales. They were planning the same tool for WP but they they quit. The main reason was that SC sales were really low, so the plugin.
I do not know how many licenses they sell a month but it is rather very low number and it is getting lower by month, because I have not seen one big upgrade in few years. All they do is putting band-aid on a very old and sick patient.
The cusomter ignorance is a biggest obstacle. It is like viscious circle. Cannot afford new features, because there is no budget. We do not have a budget because “we do not sell enough licenses” and we do not sell enough because there are no new great features…