Smart move, to keep already translated strings. I would think it should check the language also, to avoid conflict of multipel translation strings of the same language.
Smart move, to keep already translated strings. I would think it should check the language also, to avoid conflict of multipel translation strings of the same language.
Hi @mwweb this is the fix for the issue you reported in issue #53 please test this version and let me know if the error continues.
Hi @mwweb this is the fix for the issue you reported in issue #53 please test [this version](https://github.com/vdm-io/Joomla-Component-Builder/archive/f39a877db28d7ce8bf6cede2b6a4d4057c26a835.zip) and let me know if the error continues.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Yes will still expand this translator feature more, but this is the complete basic needed function for translations of the English strings.
@@ -3241,0 +3331,4 @@}else{// remove the string since no translation found and not linked to any other componentAdded a purge function the clear unused language strings from the database and unlink them from the related component during compilation.
Oops typo!
Bug!!
@@ -3241,0 +3331,4 @@}else{// remove the string since no translation found and not linked to any other componentWorks well, wonder if it should run every time.
Tested it and seems to work as intended.
Smart move, to keep already translated strings. I would think it should check the language also, to avoid conflict of multipel translation strings of the same language.
@@ -621,2 +629,4 @@$componentCounter = ' - <small>' . JText::_('COM_COMPONENTBUILDER_USED_IN') . ' ' . count($item->components) . '</small>';}// load the languages to the stringif (ComponentbuilderHelper::checkArray($langBucket))nice tweak 👍
@mwweb how is this release working for you?
I haven't had a chance to look at it. I will try to today.
Hi @mwweb this is the fix for the issue you reported in issue #53 please test this version and let me know if the error continues.
Can we get this PR merged!
@Llewellynvdm I think it is stable enough to merge this Pull request. So we can get some of these fixes out to all as the next release.