Skip to content
This repository has been archived by the owner on Feb 9, 2019. It is now read-only.

Automatically create associations of selected languages #4

Open
wants to merge 17 commits into
base: staging
Choose a base branch
from

Conversation

Wang-Yu-Chao
Copy link
Contributor

Pull Request for Issue # .

Summary of Changes

Create a modal which displays all content languages when clicking "save". Users can select some of them and associations in these languages will be created. This processes can be automated.

Testing Instructions

Expected result

image

Actual result

Documentation Changes Required

@infograf768
Copy link
Contributor

See my comment in the other PR.

Not sure what to test for here. Looks like the fallback language has no impact. (Still don't understand what it is supposed to do 😃 )

This is what I did:
First enabled the languagefilter. 3 content languages: fr-FR, de-DE and en-GB
Then created 3 root categories, 1 per language.
screen shot 2018-06-04 at 08 21 16

Then created an article tagged to English in the English category.
Then, after a first save, displayed the Associations tab for that article.
Clicked on Test. The modal displays the 3 languages. No action possible except close.
Then through the Association tab Created a new Article tagged to French, assigned to French Category.
I get
screen shot 2018-06-04 at 08 26 26
and when clicking on Test
screen shot 2018-06-04 at 08 26 40

No visible change in com_associations (Target is still broken in 4.0-dev).

Therefore if the test is to see if the modal is showing when clicking on the Test button and displays the existing Associations for each Language, then it does indeed.

@infograf768
Copy link
Contributor

Hmm, one afterthought.
If the intention is to automatically CREATE associated articles which would be the copy of the item edited but tagged to each other content language, these new articles will necessarily have to be edited IMMEDIATELY because (at minimum) their category would NOT fit (except when the original category is set to ALL languages).
Example: a French article would be assigned to an English category...
This is why com_associations has been created : to create new associations via the Copy reference to target function and then edit them at once.
This goes further if this automatic association also concerns menu items (which menu and levels) or categories (levels).

@@ -99,6 +99,10 @@
<?php if ( ! $isModal && $assoc) : ?>
<?php echo JHtml::_('bootstrap.addTab', 'myTab', 'associations', JText::_('JGLOBAL_FIELDSET_ASSOCIATIONS')); ?>
<?php echo $this->loadTemplate('associations'); ?>
<a class="btn btn-primary" data-toggle="modal" role="button" href="#ModalSelectArticle_auto_associations" title="Test Auto Association">
<span class="icon-file" aria-hidden="true"></span>Test
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Replace hard coded Title and Name by a Language Key like _MAKE_ASSOCIATIONS

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it 👌

@Wang-Yu-Chao
Copy link
Contributor Author

@infograf768 Coding is not finished yet and sorry about confusion 😛 . I'll complete this in later commits.
Category is really an issue and I'll inspect that carefully. In this PR I'm trying to implement the "automatically creating association" only for articles. Menu items and categories will be concerned after it.

@infograf768
Copy link
Contributor

Category is really an issue and I'll inspect that carefully. In this PR I'm trying to implement the "automatically creating association" only for articles. Menu items and categories will be concerned after it.

I wish you good luck. This is imho redundant with com_associations with very important side-aspects. If some improvements have to be done, it is there.

@coolcat-creations
Copy link
Contributor

I have an Issue creating a new Language with this PR...

grafik

@Wang-Yu-Chao
Copy link
Contributor Author

@coolcat-creations I haven't found this bug ... You could try PR #3 in which I fixed some bugs.

@coolcat-creations
Copy link
Contributor

Probably something wrong with my checkout... I can't create a new content language and the fallback field is missing too.

@chmst
Copy link
Contributor

chmst commented Jun 7, 2018

@coolcat-creations please check your database if you had an older version. The table #__languages must contain a field fallback_lang:

CREATE TABLE bak_gsoc_languages (
lang_id int(11) UNSIGNED NOT NULL,
asset_id int(10) UNSIGNED NOT NULL DEFAULT '0',
lang_code char(7) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL,
title varchar(50) COLLATE utf8mb4_unicode_ci NOT NULL,
title_native varchar(50) COLLATE utf8mb4_unicode_ci NOT NULL,
sef varchar(50) COLLATE utf8mb4_unicode_ci NOT NULL,
image varchar(50) COLLATE utf8mb4_unicode_ci NOT NULL,
description varchar(512) COLLATE utf8mb4_unicode_ci NOT NULL,
metakey text COLLATE utf8mb4_unicode_ci NOT NULL,
metadesc text COLLATE utf8mb4_unicode_ci NOT NULL,
sitename varchar(1024) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
published int(11) NOT NULL DEFAULT '0',
access int(10) UNSIGNED NOT NULL DEFAULT '0',
ordering int(11) NOT NULL DEFAULT '0',
fallback_lang char(7) COLLATE utf8mb4_unicode_ci NOT NULL, <------------------------
params text COLLATE utf8mb4_unicode_ci NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;

@Wang-Yu-Chao why is this field char(7)? Wouldn't it be better to use a ID of the respective language?

@Wang-Yu-Chao
Copy link
Contributor Author

Wang-Yu-Chao commented Jun 8, 2018

@chmst I use the same type as lang_code field, since in #__content, #__menus and other tables, language fields are all language code rather than language ID. So I guess using language code could avoid converting ID to lang_code.
image

@coolcat-creations
Copy link
Contributor

I see I have the field in the database - but strangely not in the view - although I checked out this PR...

name="state"
type="status"
onchange="this.form.submit();"
>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we have the state "archived"? If not, use filter="*,0,1,-2"

@joomleb
Copy link

joomleb commented Jul 3, 2018

Hi guys,
in my opinion the modal popoup is not the simple integrated way.
I summarize my point of view here: #3 (comment)

@infograf768
Copy link
Contributor

Tested again.
Using the Save (or Save and Close) button is not user friendly (not obvious and the modal always displays). The button in the Associations tab was a better idea imho.

As I already noted, the article is still just copied with a different name and alias, but with the same category which makes the feature useless.

I guess that in the case of articles, a solution could be that each language in the modal should have a Select/Create for its category and that the modal would throw an error if no category is defined when using Create an therefore prevent creating the new associated languages.
Something like:
modal

It means that for other type of items we would need :
Menu items => Select/Create Menus + Select Parent
Categories => Select/Create parent, etc.

IMPORTANT: Note that the only advantage vs com_associations is that one would create multiple associated items at the same time with an improved title/alias. It would never save the effort to edit each item as it is only a copy of the original.
The disadvantage is that, instead of using centrally com_associations to implement this improvement, one has now to create the necessary code for each component concerned, and then go to com_associations or to each manager to modify the items which are marked as Checked out.

We still have an issue in 4.0 displaying the associations for categories, whether in the cat manager or the tab when editing a category. See joomla/joomla-cms#20692

Question: What is the difference between a simple Create and Create & Remember ? (Which are both hardcoded btw and not language strings. Same for modal title which is also hardcoded.)

BTW: the instance of 4.0-dev used for staging is quite old.
@zero-24 Can you update it. Maybe just after #20692 is merged?
@Wang-Yu-Chao Then you will have to update your branch

@coolcat-creations
Copy link
Contributor

@infograf768 thanks a lot!

Associated Categories
Yes we planned to put the created articles in the associated category of the category the parent article is inside. If no category is associated the user could get a message that the articles have been assigned to the same category and if its not his desired behaviour he could associate a category.
Hope that makes sense?

Remember Option: Only ask once, remember for later
Create and Remember is there to not bother the user all the time with the modal and if all these languages should be created. The modal will appear probably only once on a multilingual site, the user let's the modal remember the decision and will not be asked again (can change the settings in the com_associations configuration)I like your idea to put these settings into the associations tab. Then we could have global settings and change them according to the authors needs. However the article will be crowded with options then, the user maybe will not need ever again. We can discuss this...

Loading Root Article Contents until translation is done

IMPORTANT: Note that the only advantage vs com_associations is that one would create multiple associated items at the same time with an improved title/alias. It would never save the effort to edit each item as it is only a copy of the original.

I would say, in the first moment it's even not a real copy. Until the user opens the associated article, this "link" should show always the contents from the parent with a message that the content has not been translated yet. Just if the user opens the associated article he can load the root articles text into it and change it / and or paste the translation in.

How could that possibly be solved?

If the not translated article is called and has a translation missing flag it will show automatically the contents of the root article with the message that the content has not been translated yet.

If the user opens an article with a translation missing flag it will be empty, but has a button to load in the root article data into all fields (editor, custom fields) if wanted. This button should be able to be hooked in by extension developers so someone could do a google translate or whatever button to retrieve translated contents. The user can change the translation state/flag to translated after work is done. (Maybe with Joomla Workflow component)

If the root article is changed AFTER the associated article with translated flag the associated article will get a translation outdated flag.

The user will be able to check the changes and to remove the translation outdated flag if wanted. If wanted a "this translation might be outdated" message can be displayed above each content with a translation outdated tag.

@infograf768
Copy link
Contributor

Yes we planned to put the created articles in the associated category of the category the parent article is inside. If no category is associated the user could get a message that the articles have been assigned to the same category and if its not his desired behaviour he could associate a category.
Hope that makes sense?

This would require categories to be already associated. Therefore making the feature more complex. An error message is not the solution imho. Specially saying that the article is created in the same category. Remember: A site can have a category set to All languages containing items set to different languages, but it is not advised at all as it may have unforecasted consequences when drilling down/up.

Please consider my proposal instead. It is much safer and easy to implement.

For the rest, I stand with my former comments: you are creating here a very heavy alternative to com_associations instead of improving it.

As I see it, what we simply need is, IN BACKEND, to tag with a translated flag (OK flag for me) the associated articles when saved the first time and it is good to go (and generally the associated items) and a translated oudated flag (Modified Reference flag for me) when the reference item has been modified. Flag that would be changed when the associated item is saved again. These flags should show in the Managers as well as in com_associations.
(As you know well, we should not use the term translated when we use associations.)

Proposing in frontend an associated item which is not complete at all should just be forbidden. The item should be unpublished.
To display a message telling the frontend user there is no associated item in that language when he switches language through the switcher is a good idea.
No use to load the reference item imho. The user just needs to know he can continue browsing in that language by going to the specific home or go back to the item he was browsing before he switched (links in the message).

I guess you are not expecting what I am saying here, but we have to be realistic and centralize features in joomla. Com_associations is in core to be used and improved.

You want to create associations automatically, still incomplete?, do it there. They will be ready to edit to fit. Tag with Complete or Incomplete, and Outdated when the reference item has been modifed and we all will get what we want.

@joomleb
Copy link

joomleb commented Jul 6, 2018

Hi infograf768,
you wrote: "...you are creating here a very heavy alternative to com_associations instead of improving it..."
I'm totally agree. Sorry, but, as a joomler from its foundation (2005) and with a lot of Multilanguage portals on my back, I have to say and add: really a "useless" alternative, too complicated and not user friendly. I mean, it does not help multilanguage sites administrators.
I hope someone else here, over jreys, will read my comments and reconsider this project:
#3 (comment)
#3 (comment)

@coolcat-creations
Copy link
Contributor

This would require categories to be already associated. Therefore making the feature more complex. An error message is not the solution imho. Specially saying that the article is created in the same category. Remember: A site can have a category set to All languages containing items set to different languages, but it is not advised at all as it may have unforecasted consequences when drilling down/up.

Yes, thats what I wrote above. Either you have associated categories or the items will be put into the same category. It would not make much sense to define only one category for all other languages (thats how I understood your proposal). Either the user had built up a structure before and when saving a category the user accepted joomla to create the automatic associations for those - or the user did not do this because he has only one category for all items then they will be created in there. I did not speak about an error message at all.

@infograf768
Copy link
Contributor

It would not make much sense to define only one category for all other languages (thats how I understood your proposal).

This is not what I meant. Sorry. My fault. The screenshot may be wrong. I proposed to add IN the modal a way to choose or create the category for each item. The Select/Create category should in fact display for each item. I guess the reason I did not add it for the first item in the screenshot is because that item was already associated the old way and it had a category (the correct one).

If no category is associated the user could get a message that the articles have been assigned to the same category

That, for me, IS de facto an error message. Adding a French article in an English category is definitively wrong.

@coolcat-creations
Copy link
Contributor

For the rest, I stand with my former comments: you are creating here a very heavy alternative to com_associations instead of improving it.

As it's part of com_associations I am not sure why you would see it as an alternative.

As I see it, what we simply need is, IN BACKEND, to tag with a translated flag (OK flag for me) the associated articles when saved the first time and it is good to go (and generally the associated items) and a translated oudated flag (Modified Reference flag for me) when the reference item has been modified. Flag that would be changed when the associated item is saved again. These flags should show in the Managers as well as in com_associations.
(As you know well, we should not use the term translated when we use associations.)

Ok I think with the flagging we have the same opinion ?

Proposing in frontend an associated item which is not complete at all should just be forbidden. The item should be unpublished.

Let the site owner decide if it's unpublished or not. Like you see, Amazon is doing that too. They provide the english content to the german customer and state above that the translation is in progress. In my eyes a very good customer service because at least I have something to read into even if its not translated yet. Reference Link for french: https://developer.amazon.com/fr/docs/custom-skills/speech-synthesis-markup-language-ssml-reference.html

To display a message telling the frontend user there is no associated item in that language when he switches language through the switcher is a good idea.

Yes, thanks - thats indeed great we can think of that too...

No use to load the reference item imho. The user just needs to know he can continue browsing in that language by going to the specific home or go back to the item he was browsing before he switched (links in the message).

I don't think the user comes always from a "switched" state. He probably is browsing the website all the time in his own language and would never think of that the other language provides more information than the site he is browsing. Providing the whole content set (if the siteowner wants to do that) is a good customer service. You might not see this useful from english to other languages but often backwards. Example: Someone has a website in 5 languages (Spanish, Italian, Chinese, German, English) - Now Austrian and Turkish will be added. Fun fact about Austrian is, that it's 98% like German - so it would be need only 5 items/articles to be "translated" and the other 1500 items pointing just to the german contents. And not to the copy of that items, because this would mean you have to maintain always the copys too. In that case the siteowner would disable even the "not translated yet message" There would be 1500 associated items that only function as "pointers" - Next Example for turkish: The turkish company is perfectly happy about having the Homepage, the Contact Page and the Page about the Company in turkish, everything else will be shown in english (because it will be not possible to translate 1500 items in short time). But how should the user know that other contents exist? Solution: Turkish falls back to the English language and points to the contents of those items. Maybe one of those pages will be amazingly popular (page hits) and so the company knows that it would be probably better to translate the articles above xxxx page hits.

Reading your comments I think we are quite on the same track but maybe a meeting on skype or some kind of hangout will help us to figure out the specific needs, concerns and to figure out things faster?

@coolcat-creations
Copy link
Contributor

That, for me, IS de facto an error message. Adding a French article in an English category is definitively wrong.

Yes, depends how the users work... but you are right. I would expect the user to have associated categories too.

So we could manage it like that: If the category has no associations the modal proposes to create the associated categories too ? Is that a solution?
Or like you thought to create those categories on the fly for each language... We just need to decide for one of those solutions.

@coolcat-creations
Copy link
Contributor

coolcat-creations commented Jul 6, 2018

@joomleb Thanks and appreciate your comments about the project too. But from what I can say we will NOT provide 3rd party translations services in Joomla. But thats something that definetly will be considered to put at least something to "hook into" for 3rd party developers. But not provided by core.

To break the scope of this GSoC down to just one sentence it's focusing on:
Automatically create associated items on root item creation
to reduce the time expenses for creating and linking associated items manually.

Everything else is an absolutely nice to have and I am looking forward to push things forward also after GSoC. The part about "outdated" flags and information is a part that is thankfully done by our great Mentor Lavinia, who is working on that part for her Bachelor degree on the university of Gießen.

@joomleb
Copy link

joomleb commented Jul 6, 2018

Hi Elisa,
many thanks for your reply, but reduce the comment to what I wrote with: "...from what I can say we will NOT provide 3rd party translations services in Joomla...", at least, is a little bit offensive to my humble intelligence. Here the cases are:
A - You didn't read step by step all what I posted in the two comments > I respect your choice, I cannot do nothing
B - I have not been able to express what I mean with my poor English > In this case if you make me questions I can answer and try to explani it as better as I can
C - You don't want read them carefully > I respect your choice, I cannot do nothing

In my "resumen" #3 (comment) and in the reply to jreys #3 (comment) there are my suggestions, my opinions and a lot of questions...

@jreys
Copy link
Contributor

jreys commented Jul 7, 2018

Hi @joomleb,

Pretty sure Elisa wasn't trying to be offensive 🙂 The reason for not depending on 3rd party services/software is because of the constant evolution and having to adapt to it, by using those 3rd party services while making some stuff easier (the translations) and more direct, imagine if one of those services completely changes. The way it is included into this component has to be changed, some sites could break before a patch could fix that, do you understand?

I know ReCaptcha is being used but it's more about safety (against bots, etc.), TinyMCE is a lib and as long as it has a stable version there are no problems using that! Google/Bing translate are a good plus to have but they don't solve a real problem, they just make things easier.

That's why being dependent on such things is not advisable, if a 3rd party extension wants to do that sure, but it won't be associated to Joomla core 😉

Btw your english is alright, I've seen worse 😂

@infograf768
Copy link
Contributor

Reading your comments I think we are quite on the same track but maybe a meeting on skype or some kind of hangout will help us to figure out the specific needs, concerns and to figure out things faster?

It would be a good idea to discuss indeed on skype or glip as I think we are not on the same track concerning the fallback language, the reference language, the place where to create automatically the associations, the select of categories, etc..
Not after 19:00 (European time) for me.

@coolcat-creations
Copy link
Contributor

Hi @joomleb as @jreys says it was absolutely not intended to be offensive, I had limited time but wanted to respond to your post at all.

$this->filterForm = $this->get('FilterForm');
$this->activeFilters = $this->get('ActiveFilters');

if (!Associations::isEnabled())
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So many uncommented lines, don't forget your code will be read by other people and it's hard to modify code that you don't know what is doing.

I suggest you do the following:

// Comment
<block of code>

For example:

// Getting form data
$name = $input->get('name');
$age  = $input->get('age');

// Sanitizing name
if (strlen($name) === 0)
{
    \JFactory::getApplication()->enqueueMessage(\JText::sprintf('ERROR_MSG_NAME', $link), 'error');
}

// Sanitizing age
if ($age < MIN_AGE || $age > MAX_AGE)
{
     \JFactory::getApplication()->enqueueMessage(\JText::sprintf('ERROR_MSG_AGE', $link), 'error');
}

// Preparing an array to store into the DB
$data['name'] = $name;
$data['age']  = $age;

// Store form data into the db
$model->store($data);

This was just an example, not real code, so you can make better comments 😉

if (array_key_exists('support', $details))
{
$support = $details['support'];
$this->typeSupports = $support;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not $this->typeSupports = $details['support']? Doesn't make the code more readable to create an extra var.

if (array_key_exists('fields', $details))
{
$fields = $details['fields'];
$this->typeFields = $fields;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here

}

// Store user's decision
if ($remember && !empty($langIds))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This if/elseif code looks a bit repeated, can you find a way to generalize it?

}

// Store the row.
if (!$contentTable->store())
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These 2 ifs could become an OR:

if (!$contentTable->check() || !$contentTable->store())
{
    $this->setError($contentTable->getError());
    return false;
}

else
{
$this->set('decision', '');
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need for the else statement, just do $this->set('decision', ''); before the previous IF, also lots of uncommented code, keep it tidy 🙂


$itemId = $displayData->get('Item')->id;
$modalId = 'associationAddAssociations';
$modalTitle = 'Multilingual Associations';
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why isn't this a language string?

'modalWidth' => 80,
'footer' => '<a type="button" class="btn btn-secondary" data-dismiss="modal" aria-hidden="true"'
. ' onclick="jQuery(\'#associationAddAssociations iframe\').contents().find(\'#closeBtn\').click();">'
. JText::_('JLIB_HTML_BEHAVIOR_CLOSE') . '</a>'
Copy link
Contributor

@chmst chmst Jul 10, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably the Close button could be simpler:
'<button class="btn btn-secondary" data-dismiss="modal">’ . JText::_('JLIB_HTML_BEHAVIOR_CLOSE') . '</button>
should do it as well and is correct semantic.

@zero-24
Copy link
Member

zero-24 commented Jul 11, 2018

BTW: the instance of 4.0-dev used for staging is quite old.
@zero-24 Can you update it. Maybe just after #20692 is merged?

@infograf768 Just as a update it seams i have missed this mention here. But joomla/joomla-cms#20692 is not merged yet so also not included in the regularly sync of the master branch yet.

@infograf768
Copy link
Contributor

@zero-24
Let's just update master. After some discussions, @Wang-Yu-Chao is going to start again from scratch with a new branch.

});

window.parent['fillFields'](values, remember);
window.parent['closeModal']();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is an API method to close the modal:
window.parent.Joomla.Modal.getCurrent().close()

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dgrammatiko
This PR is obsolete.
All is now done in new branch new-staging.
#6

zero-24 pushed a commit that referenced this pull request Sep 6, 2018
* Load correct core files of override files (#2)

Start implements loadcorefile() in administrator/components/com_templates/Model/TemplateModel.php

* CS (#3) Coding Standards

* codingstandards

* codingstandards (#4)

* Test (#6)

Phase 2 (2 part) Mechanism to find correct core file and implementation.

* Remove Notice: Only available for html-folder

* Remove Warning if core file not found (#11)

Thanks.
So one part of the issue joomla-projects/gsoc18_override_management#12 is done.

* Implement the diff view in template manager 

Implement the diff view in template manager

* coding standard (#17)

* fix diff (#18) Fix bug in path in case of administrator template override.

Fix bug in path in case of administrator template override.

* Notification after update and TEST (#16)

Find changed files of overridden files and show message.

* coding standard (#21)

* correction

* correction (#26)

* Correcthtmlpath (#27)

* correction

* change oldhtml to newhtml

* List of updated override files. (#30)

* addcss (#34)

* Final Product  (#39)

Core and Diff view
Updated override history list.
Quick icon notification plugin.
Override control plugin.

* save 3 lines :)

* New feature show status. (#47)

show status in com_template view templates

* link

* corrected namespace

* Button to Switch (#35)

* wip add Switcher

* wip style switcher

* wip style switch make inline and change on off text

* wip start with js

* wip js

* wip delete buttons and make js more robust

* wip save to storage

* wip delete old code

* wip

* wip lint

* wip css

* set default value for switcher

* wip make switcher blue

* wip

* wip

* build

* correct names

* create new functions

* fist test code

* use onchange

* undo installer.min.js

* add forgotten new line at the end of css file

* correct align

* correct compare.es6 - only deleted the toggle part

* correct compare.js - only deleted the toggle part

* wip

* reduce timeout

* wrap in funcitons

* wip

* add use strict to both js-files(compare and toggle)

* add the timeout value of 500 again, because 200 are not enought in my case

* use css class 'active' for toggle views

* add strict

* time out for editor

* wip

* improvments use newActive and switch

* correction

* width of switcher-spans

* correct align

* do not use global

* wip

* removed timeouts

* JTEXT to TEXT

* forgotton last line

* deleted duplicated comments

* css fix align

* use unnamed functions in es6

* Sql files for fix database (#50)

* sql files for database fix

* delete space

* Suggestion for displaying Dates in view updates files (#52)

Correct Dates and do not use date of file any more

* Store Date as UTC and show it in server time zone (#57)

* modified and created date are created and stored in UTC

* convert dates for displaying in model

* spar a loop

* normalize timezone in view

* use language constants for dateformat

* JToolbarHelper to ToolbarHelper

* CS

* namespace

* plural

* name

* clean

* text

* fx

* sin

* files

* s

* Suggestion for language strings (#60)

* language strings

* correct typo

* delete media folder plg_quickicon

* add folder plg_quickicon to build/media_src

* delete files in media folder

* Move media folder - System (#66)

* multi

* cs

* delete files in media folder for joomla toolbar (#67)

* Fix button switchers style. (#70)

* button

* CS

* changed uitab.addTab for updated files

* Bring back core.js changes. (#69)

* core.js

* const

* fix

* form

* core

* hound

* CS

* scopr

* grid

* alpha

* cs

* lang

* only override file

* lang

* override lang installer

* Cs

* sub

* Update list of core extensions (#71)

* Language changes (#76)

* update

* Update en-GB.com_templates.ini

* override JLIB_HTML_PUBLISH_ITEM

this is the hover text on the publish icon in the list of files

* Change icon (#74)

change the icon to use an outline for more consistency

* lang

* not core (#75)

* not core

* Update en-GB.plg_installer_override.ini

* namespace

* cs

* Updated files (#82)

* Update default_updated_files.php

* Update en-GB.com_templates.ini

* Update en-GB.com_templates.ini (#81)

* Update en-GB.plg_quickicon_overridecheck.ini (#80)

* Update en-GB.plg_quickicon_overridecheck.ini (#79)

* remove space (#78)

* Update en-GB.plg_quickicon_overridecheck.ini

* Update en-GB.plg_quickicon_overridecheck.sys.ini

* remove hardcoded id

* null get function

* state

* clean

* More changes "core" to "original" (#85)

* cs

* update

* plural
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants