Categories > TinyButStrong general >

Joomla Plug-in 1.20 aka 1.0.2 external script location

The forum is closed. Please use Stack Overflow for submitting new questions. Use tags: tinybutstrong , opentbs
By: Bruce Decker
Date: 2009-09-30
Time: 07:24

Joomla Plug-in 1.20 aka 1.0.2 external script location

Hi Skrol:
I just got around to playing with the latest Joomla plug in.  I really like the restructuring into _comm and _spec.  I notice something that perhaps has changed in this release.  In the old release, in the plug-in parameters, there was a 'script location' param.  The main script prepended this to the script name and I really liked that solution as it makes it easier for my users not to have to understand where the scripts are installed.  However, in the new version, it looks like we just include($Script) and do not worry about the script location param.  To test, I changed my {tbs} script directive to specify the entire script path and it works. I will try to look about and see where the joomla plug-in params are kept and perhaps I can suggest a mod that will restore this useful functionality.

Again, nice work!

Regards,

Bruce Decker
Colorado
By: Bruce Decker
Date: 2009-09-30
Time: 07:29

Re: Joomla Plug-in 1.20 aka 1.0.2 external script location

Hi Skrol:
Hold on.  I need to re-check my xml file and match up the param names in case I hammered the .xml.
-BD
By: Bruce Decker
Date: 2009-09-30
Time: 07:38

Re: Joomla Plug-in 1.20 aka 1.0.2 external script location

Yep, of course, it was me.  Re-loaded .xml and all is fine.  Now, get to play with the new params stuff!
By: Skrol29
Date: 2009-09-30
Time: 14:23

Re: Joomla Plug-in 1.20 aka 1.0.2 external script location

:)
this feature has not been touched in the news release.

By the way, I wonder to have you opinion as a user of the Joomla plugin:

When the plugin is installed for the first time, the default permission allows all writers to use Direct MergeBlock on all articles. It means that a writer with bad intention can create a new article or modify an existing one in order to have it displaying any content of the Joomla database. No modification can be performed by this way. Do you think this is clear for Joomla admins, or do you think that the default permission should be restricted to none articles?





By: Bruce Decker
Date: 2009-09-30
Time: 15:57

Re: Joomla Plug-in 1.20 aka 1.0.2 external script location

Hi Skrol:
My opinion is the following...
1) I've looked at the pros and cons of the different methods and I'm going to stick with 'external script only' from a specified location.  I think it makes sense to separate the 'data provider' from the 'article'.  I don't want my writers to be authoring SQL.  I want control of how data is accessed from within articles.

2) If I did allow direct mergeblocks, I would want to go with the most restrictive configuration available. 

Thanks,

Bruce Decker