Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation and Context
I don't know if this intended or not, but the forced sc override trigger as true gives a "bug", forcing the class name to be
plugin_myplugin_plugin_myplugin_overridenSCname_shortcode
(yes, the two first sentence twice) & file name to beplugin_myplugin_overridenSCname_shortcode.php
I also would like to know what's the intended "override", since both override options won't really "override", they simply load the myplugin shortcode, without nothing from the original overriden plugin shortcode....
Description
Just changed the documentations next to the function because i don't know if this is the intended behaviour or not....
How Has This Been Tested?
Current github code of e107, and tested calling
e107::getScBatch('corescname', 'mypluginscname', true);
The
e107::getScBatch('corescname', 'mypluginscname', 'corescname');
call works as intended, overriding the corescname shortcode...Types of Changes
Checklist