ZCA Bootstrap 4 Template [Support Thread]

[royaldave]

There's no "two-arrow" button in the base Bootstrap template, perhaps something you've added?

Hi

I mean the update button - with the two swirly arrows..

[lat9]

Hi

I mean the update button - with the two swirly arrows..

I'm not able to reproduce this behavior. Are there any myDEBUG*.log files or errors noted in the browser's console-log?

[mikecnz]

Hi again,

And thanks for the feedback, I've managed to get the define pages showing in a side box, but I cant see an option for having them in the header or footer provided. I'm finding Bootstrap to be a bit more fiddly in the admin settings than my previous template - but I'm making progress.

Now I've got an issue with the EZ-pages, and I'm unsure what's causing it.
Running Zencart 2.0.1, only mods are OPC and CKEditor5.

I edited an Ezpage to include some bootstrap styling as follows:
<img class="float-left pr-3" src="images/Bulk-Honey.webp" alt="Bulk Honey in varying size, as supplied by Cammell's Honey">
Click the Update button, visit the page and see that no change has been made, revisit the source and see the code has been altered back to:
<img src="images/Bulk-Honey.webp" alt="Bulk Honey in varying size, as supplied by Cammell's Honey">

The same happens with header tags as well, only basic <P> and <img> tags seem to remain unchanged.

The same happens on the define pages as well, any styling gets stripped, but text changes remain.
This occurs whether I am using CKEditor or plain text.

[mikecnz]

Further to the above, I can make styling changes directly on the EZ page in the database and these will remain when saved.
So it appears to have something to do with making changes in the Admin editor.

[barco57]

I've managed to get the define pages showing in a side box, but I cant see an option for having them in the header or footer provided.

That would be because it doesn't exist... There is no define page bar in the header or footer.
Are you making a new version of your site in your signature?
if you are trying to reproduce the drop down menu on your current live site, there is no functionality like that in either the bootstrap template or responsive classic. It was basically a plugin included in winchester responsive that provides the dropdown menu

the class tag being removed regardless of ckeditor5 or text editor is probably over-sanitization of the input...

The footer layout in your current site are a result of the flexlible footer plugin included in the winchester responsive template

[barco57]

ok, testing shows that Ckeditor5 is what is stripping the class off the image tag.
So another thing that Ckeditor 5 causes an issue with

[mikecnz]

ok, testing shows that Ckeditor5 is what is stripping the class off the image tag.
So another thing that Ckeditor 5 causes an issue with

Ok, so to workaround this currently I am pasting code directly into the database - it may be slow, but it works.

Another couple of questions:
In the documentation (https://github.com/lat9/ZCA-Bootstra...ecific-styling)
the following code is mentioned:
if ($this_is_home_page) {
?>
<style>
h1 {color: red;}
</style>
<?php
}
This will allow for styling of the home page, is there a list of codes for the various pages? e.g. contact us, ez pages, etc?

I assume this code could also used to load a style sheet for a specific page?
<link href="<?php echo $template->get_template_dir('.css', DIR_WS_TEMPLATE, $current_page_base, 'css') . '/mysite.css'; ?>" rel="stylesheet">

[lat9]

Ok, so to workaround this currently I am pasting code directly into the database - it may be slow, but it works.

Another couple of questions:
In the documentation (https://github.com/lat9/ZCA-Bootstra...ecific-styling)
the following code is mentioned:
if ($this_is_home_page) {
?>
<style>
h1 {color: red;}
</style>
<?php
}
This will allow for styling of the home page, is there a list of codes for the various pages? e.g. contact us, ez pages, etc?

I assume this code could also used to load a style sheet for a specific page?
<link href="<?php echo $template->get_template_dir('.css', DIR_WS_TEMPLATE, $current_page_base, 'css') . '/mysite.css'; ?>" rel="stylesheet">

The various pages can be seen by viewing the names of the sub-directories in /includes/modules/pages. To load a page-specific stylesheet, you can refer to /includes/templates/template_default/css/CSS_read_me.txt, which contains

The CSS files are sent to the browser in this order: (and alphabetically within each case of more than one match):

             style*.css   // are always loaded and at least ONE should contain site-wide properties.
language_stylesheet.css   // changes to ALL pages, when that language is used
         index_home.css   // specifically affects the home page only
          page_name.css   // changes to one page, ie: index.php?main_page=page_name
 language_page_name.css   // changes to one page, when that language is used
            c_??_??.css   // changes to all info pages in a category
   language_c_??_??.css   // changes to all info pages in a category, when that language is used
   c_??_??_children.css   // changes for all children of the specified parent. Also supports a language prefix.
               m_??.css   // changes to a manufacturer's listing page
      language_m_??.css   // changes to a manufacturer's listing page, when that language is used
               p_??.css   // changes to a product's info page
      language_p_??.css   // changes to a product's info page, when that language is used
             print*.css   // printer-friendly global usage site-wide changes for printing-only
             page##.css   // EZ-Page -- css specific to a numbered EZ-page ... ie:  page21.css would be for EZ-Page number 21 ... ie: for the URL index.php?main_page=page&id=21

The 'stylesheet.css' is expected to load first and should contain the bulk of your CSS selectors. Each file loaded takes priority over previously loaded file(s). To save loading time, only new selectors or selectors whose properties you wish to change should be in the optional CSS files. You can have different overrides for the same page, in different languages, because the two would never be called at the same time.

If someone selected the French language on your site, the 'french_stylesheet.css' would also be loaded. It should only contain the site-wide changes you want to make to 'stylesheet.css'. For example, change a 'background-image' for your French customers.

If someone went to any of the other pages, that page's CSS file would be loaded. Possibly you want different 'background-image' & 'background-color' on each of 'page_x' pages. Possibly you do not want a border around '.plainBox' most of the time, but on a couple of pages you do... and on one of those pages you want it in black and the other in red.

Possibly you created a NEW tag and did a <span class="newtag"> in your Privacy Statement. It is defined in only one CSS file, 'german_privacy.css' as '.newtag { text-transform: uppercase }' Because, in Germany, that phrase must be in all CAPS, but not in other countries.

Use your CSS files and the standard tags as much as possible, just change their properties when needed. If possible, DON'T HACK the core code. Use your CSS files to do the work for you. When the style coding has been removed from the ZenCart code and people have to decide if they want to go without the upgrade ~or~ undo all their hacks and finally learn about CSS... your site will still be up and running.

Additional information is contained in the Zen Cart documentation.


Adapted from ideas presented by
Juxi Zoza
03/15/05

[jpda]

@mikecnz

if ($this_is_home_page) {
?>
<style>
h1 {color: red;}
</style>
<?php
}
This will allow for styling of the home page, is there a list of codes for the various pages? e.g. contact us, ez pages, etc?

See this post: https://www.zen-cart.com/showthread....28#post1391428

jpda

[royaldave]

I'm not able to reproduce this behavior. Are there any myDEBUG*.log files or errors noted in the browser's console-log?

Not seeing anything, no.

I have reverted to using responsive classic in this setup and its now working as should.

No idea what the issue is - I'm faced with starting over on this upgrade and checking the shopping cart at each step.