-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[4.1] Child templates 2/2 [clean] #35998
[4.1] Child templates 2/2 [clean] #35998
Conversation
administrator/components/com_templates/src/Service/HTML/Templates.php
Outdated
Show resolved
Hide resolved
Co-authored-by: Brian Teeman <[email protected]>
Co-authored-by: Brian Teeman <[email protected]>
Co-authored-by: Brian Teeman <[email protected]>
0a1f1a9
to
1ed0770
Compare
@brianteeman do you know if the |
Sorry I don't know. I will do some research tomorrow. Caveat a lot of the examples on that site are not very good |
Do you have a solid example for tree view? I use some of the links from w3c/aria#1311 |
Not at my pc but the link I shared the other day in the media manager pr looked good |
It's sharing the same code as https://w3c.github.io/aria-practices/examples/treeview/treeview-1/treeview-1b.html |
@dgrammatiko Looks ok to me. But can it be that more than one template style for a child template is not supported? When I make the template style of the child template be the default, I get no CSS from the parent loaded. Backend template styles: |
The names for your child templates are off, should be
No, styles are just the JSON blob from the db so there shouldn't be a limit on the copies...
Does the folders |
@dgrammatiko Yes, it exists. I've created another child with a more suitable name but that did not help. Another thing I have noticed is that I can created new child templates, but I cannot delete them. Is that by design or will the delete come later with another PR? |
@dgrammatiko It seems it loads the template css files from the media/templates/site/cassy/css folder, but stuff from sub-folders "global", "system" and "vendor" is not included. |
P.S. Could that be an issue of the Cassy template? |
Actually, you can already, got to System->Extentions, select templates in the filters and then delete any child template (probably not the most intuitive workflow)... By the way, can you remove all the preexisted templates and try again your tests, something seems awfully wrong but I can't pinpoint what it is... |
@dgrammatiko I've tried again from scratch with a new installation of this branch. This time only one language, no template style copies, nothing special. I only installed the Cassy template and made it's template style the default. That worked, i.e. frontend looked ok. Then I have created a child template named "Child_1", so the generated name at the end was "Cassy_cild_1"- That worked. But then I make the template style of this child be the default, the frontpage looks like in my screenshot, i.e. some but not all CSS seems not to be loaded. |
@dgrammatiko Is it possible to test with both PRs #35874 and this here together? Or do they conflict somehow? |
Yeah there was something off in the cassy template, try this Cassy_new.zip
I think there is nothing that conflicts, so they could be tested together. Remember to apply the db changes... |
@dgrammatiko I have just tested now with the both PR's merged together in a branch. I don't have the problem when creating a child template of the (now inheritable) Cassiopeia and then make the template style of that child be the default. So it either is an issue with Cassy or it needs both PR's together. |
I have tested this item ✅ successfully on 7a95857 The right editor.css is included when editing with TinyMCE in backend, regardless if the default template style is one of an inheritable or a not inheritable template or the child template of an inheritable template. I've tested this PR alone with the core templates being not inheritable and the inheritable Cassy template installed (fixed version), and I also have texted it in combination with PR #35874 so the core templates were inheritable. Both worked. If there are minor glitches which I've missed in my tests, I think they can be fixed later. This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/35998. |
I have tested this item ✅ successfully on 7a95857 This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/35998. |
RTC This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/35998. |
administrator/components/com_templates/tmpl/template/default_folders.php
Outdated
Show resolved
Hide resolved
…olders.php Co-authored-by: Quy <[email protected]>
I've added back the previous test results in the issue tracker since the last commit was just the removal of an obsolete "use" statement. |
// Issue warning notice if the file is not found (but pass name to $content_css anyway to avoid TinyMCE error | ||
if (!file_exists($templates_path . '/' . $template . '/css/' . $content_css_custom)) | ||
{ | ||
$msg = sprintf(Text::_('PLG_TINY_ERR_CUSTOMCSSFILENOTPRESENT'), $content_css_custom); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove language string?
Thank you! |
joomla/joomla-cms#30522 + joomla/joomla-cms#32223 + joomla/joomla-cms#31675 + joomla/joomla-cms#35378 + joomla/joomla-cms#35612 + joomla/joomla-cms#35715 + joomla/joomla-cms#35610 + joomla/joomla-cms#35607 + joomla/joomla-cms#35788 + joomla/joomla-cms#35647 + joomla/joomla-cms#35143 + joomla/joomla-cms#36135 + joomla/joomla-cms#35998 + joomla/joomla-cms#36173 + joomla/joomla-cms#36212 + joomla/joomla-cms#36208 + joomla/joomla-cms#36206 + joomla/joomla-cms#36205 + joomla/joomla-cms#36203 + joomla/joomla-cms#36192 + joomla/joomla-cms#36191 + joomla/joomla-cms#36228 + joomla/joomla-cms#36211 + joomla/joomla-cms#36271 + joomla/joomla-cms#36270 + joomla/joomla-cms#36245 + joomla/joomla-cms#36294 + joomla/joomla-cms#36244 + joomla/joomla-cms#36242 + joomla/joomla-cms#36296 + joomla/joomla-cms#36190 + joomla/joomla-cms#36474 + joomla/joomla-cms#36297 + joomla/joomla-cms#36480 + joomla/joomla-cms#36479 + joomla/joomla-cms#36551 + joomla/joomla-cms#36366 + joomla/joomla-cms#36589 + joomla/joomla-cms#36583 + joomla/joomla-cms#36328 + joomla/joomla-cms#36515 + joomla/joomla-cms#36555 + joomla/joomla-cms#36653 + joomla/joomla-cms#36660 + joomla/joomla-cms#36657 + joomla/joomla-cms#36637 + joomla/joomla-cms#35983 + joomla/joomla-cms#36704 + joomla/joomla-cms#36708 + joomla/joomla-cms#36700 +
Pull Request for Issue # .
Summary of Changes
cassiopeia_temp
Testing Instructions
Git fetch this PR, run npm
Try every functionality in the com_templates for both core templates
Install https://github.com/joomla/joomla-cms/files/7235154/cassy_1.0.0.zip (cassiopeia with a different name)
Try every functionality in the com_templates for the installed template
Also check (with tinymce as the editor) when editing an article that the editor.css (or .min.css if not in debug mode) is loaded from the
/css
folder of the template, if such file exists. (the path can be/templates/templateName/css/editor.[min.]CSS
for existing templates ormedia/templates/site/templateName/css/editor.[min.]CSS
for templates supporting children).Actual result BEFORE applying this Pull Request
Expected result AFTER applying this Pull Request
Documentation Changes Required
Yes, this is the UI for the codename
child template
or whatever the project ends up naming the inheritable/extendable/... templates