New MVC GSOC 2014

https://groups.google.com/forum/#!topic/joomla-dev-cms/AH6piuw2IR0

http://gwilson.org/index.php/new-mvc
Funny, so modules or plugins can load core strings, but components shouldn't. Sounds like your priorities are backwards.

Also by failure you mean the user would get a different message, as supposed to currently getting an untranslated string like MY_COMPONENT_DOESNT_SUPPORT_CHINESE, because the dev didn't read that line of code.

These strings make the CMS look just as bad as the extension. 

How about say.... Using JCOMPONENT_STANDARD_ERROR_WHATEVER 

Would you still give modules and plugins priority.

Sincerely,
Mathew Lenning

Babel-university.com

P.S. This message was sent via iPhone, so please forgive any errors

> On Aug 22, 2014, at 9:27 PM, Thomas Hunziker <notifications@github.com> wrote:
> 
> In libraries/cms/model/actions.php:
> 
> > +				// Trigger the onContentBeforeDelete event.
> > +				$result = $dispatcher->trigger('onContentBeforeDelete', array($context, $activeRecord));
> > +
> > +				if (in_array(false, $result, true))
> > +				{
> > +					throw new RuntimeException($activeRecord->getError());
> > +				}
> > +
> > +				$activeRecord->delete($pk);
> > +
> > +				// Trigger the onContentAfterDelete event.
> > +				$dispatcher->trigger('onContentAfterDelete', array($context, $activeRecord));
> > +			}
> > +			else
> > +			{
> > +				throw new RuntimeException($this->text_prefix . '_ACL_ERROR_DELETE_NOT_PERMITTED');
> That would fail if a module or plugin loads the language files with such an override.
> Extensions should never override core language strings withing their language files. They must always use an own prefix.
> 
> \
> Reply to this email directly or view it on GitHub.