URL: https://docs.zen-cart.com/user/new_user_topics/change_powered_by/
Page title: How do I change the logo or the logo alt text in the header?
breadcrumb: Storeowner Docs / New User Topics / How do I change the logo or the logo alt text in the header?

Looking at https://docs.zen-cart.com/dev/code/notifiers/, there are a bunch of code blocks that overflow horizontally and, thus, wrap.

Isn't the 'standard' markdown to have a horizontal-scroll on overflow for sections delimited by '```'?

Guys, it seems like
https://docs.zen-cart.com/
redirects to
https://docs.zen-cart.com/Habitat/main

If we can instead use an index.html (perhaps maintained in this repo), we can increase the visibility of other sections of the docs; right now you have to know the URL in advance to get to them - such as https://docs.zen-cart.com/Developer_Documentation/1.6 for example.

A number of the files in this repo have a line that says FIXME. If you have time and expertise in the area, please fix.

Submitted an issue to docsy about this and believe I have a solution, but proof of application requires breaking off from that branch and incorporating the suggested changes which affects two files (not currently included in the ZC docs partials).

There actually are a few things, but the first was to address the items generated in the list.

For at least the <ul> tag issue, see:
google/docsy#271

There may also still be an issue with links within the menu that had to be captured the same way as the above was corrected.

https://docs.zen-cart.com/user/upgrading/detailed_upgrading/
The formatting of sections 1 and 3 does not appear correctly in the web view.

You keep saying doc info is generated automatically by a script. Will the script need to be run again if changes occur? Does the script create the pages? If we edit the docs.zencart, does that make a permanent change that will not be overwritten by running the script again? I can definitely get started adding info into the docs. I just need clarity here.
I'm just trying to figure out what's going on.

Originally posted by @wiztechinc in zencart/zencart#3293 (comment)

I am currently formulating an addition to the Image Preparation - how to Page but think we need to address the line up of this page first.

IMHO, the lineup should be as close to actual operation as possible. i.e., you wouldn't talk about adding attributes until you had covered the addition of products that might have those attributes.

What about swapping 1 & 2 to the 3 & 4 position which would make it:

Image Preparation- how to
Images -multiple image problems (and changing to Images - Preparing for Additional Images)
Additional Images - adding
Additional Images - disabling

I thought it was incredibly clever how EditOrdersAdminObserver.php uses generic names for the formal parameters of the update function, and then describes them in comments for each event type.

Would you please update

https://docs.zen-cart.com/dev/code/notifiers/

and describe this technique?

(While you're there, it would be great to give that article a scrub and improve the examples.)

Thank you!

Do we want to move this to the new Docs system?
https://www.zen-cart.com/wiki/index.php/Administration

If so, would some nice person volunteer to do it?

A lot of this text was written quite a while ago and just needs to be tweaked to not refer to "how things used to be" so much.

@brittainmark Please take this one - all related to PR #301. (See comments on that PR.)

Also on
https://docs.zen-cart.com/user/localization/languages/

Please capitalize "English" in the last heading,
Admin field descriptions still in english

https://github.com/zencart/documentation/blob/master/content/dev/plugins/encapsulated_plugins/directory_structure.md
When viewed in git all lines up correctly. When viewed in firefox on the zen cart site v1.0.0 and includes not correctly indented. Html
`

Sorry don't know how the document is generated so could not fix.

Where possible, (new) code should always output HTML/CSS/JS directly, and NOT use PHP to echo the HTML.

I think the only notable exception is /form to close zen_draw_form? So should be mentioned?

Initiated a post in the forum: https://www.zen-cart.com/showthread.php?226626-Display-and-operation-issues-with-docs-zen-cart-com

Where I identified that there was an issue accessing the docs.zen-cart.com site. One of the issues identified was a javascript issue that I believe I have tracked down, the question is how to obtain resolution (if it is to be resolved). It appears that the feedback.html partial file (apparently from docsy) uses a short form of javascript function assignment to a variable:

const disableButtons = () => {

and

const sendFeedback = (value) => {

While I can not comment on this being "appropriate" use or not, but in independent testing from my device, I have been able to confirm that if those lines had been written as:

const disableButtons = function() => {

and

const sendFeedback = function(value) => {

then they would execute successfully or at least not error at those line(s)...

I have found through other review that at least one file/location where this is contained in docsy is at:
google/docsy@65c93da

Where the feedback element was first incorporated.

I am making a note at that site/location about this issue as I suspect (since not finding the partial file feedback.html on this site) that the package is used/drawn from to provide the docs site. Therefore it seems that for it to be corrected it has to go through a third party and not through the ZC community.

For Cindy.

As requested in
https://www.zen-cart.com/showthread.php?226556-PHP-Fatal-error-1366-Incorrect-integer-value&p=1367454#post1367454

We just want an explanation of how order statuses are updated.

https://github.com/zencart/documentation/blob/master/content/dev/code/creating_menu.md

https://github.com/zencart/documentation/blob/master/content/dev/plugins/encapsulated_plugins/directory_structure.md

the use of the prefix v for a version number is confusing, and IMO, should be removed. versions should be 1.0.1.

referencing a software version in documentation or when referring to V 1.5.7 is 1 thing; but making the v part of the number seems wrong to me.

Can you add PRODUCT_URL_REGEX as one of the custom methods of sanitizing?

I need it for off site image retrieval (I know...it's not the best practice but the off site images will act as IMG_ALT eventually).

I am making it work at the moment by modifying init_sanitize.php:

//MIKE REMOVED FROM ARRAY BELOW - 'products_previous_image',
$group = array('img_dir', 'products_image_manual', 'products_attributes_filename', 'manufacturers_image_manual');
$sanitizer->addSimpleSanitization('FILE_DIR_REGEX', $group);

//MIKE ADDED TO THE ARRAY BELOW 'products_previous_image'
$group = array('products_url', 'products_previous_image', 'manufacturers_url');
$sanitizer->addSimpleSanitization('PRODUCT_URL_REGEX', $group);

I have added a custom sanitize file to extra_datafiles but can't, for the life of me, figure out how to obtain the same results as changing the init_santitize file.

Thanks.

Motivated by remarks on PR #47.

After installation I see my new menu items, they link to the pages I have created. But, if I close the browser/open and try to log back in I get a blank screen. I have to remove the files eg. new_tool_filenames.php to get back in. Then I have to upload the new_tool_filename.php again to see it in the menu.

Clearly, the files are writen correctly otherwise it wouldn't install.

I have tried many way. I tried removing the autoloaders and the init files but this makes no difference. I realise I am missing something, can you assist me in this matter.

Regards

In review of the html validation for the docs site, specifically using: https://docs.zen-cart.com/user/about_us/in_memoriam/ as a basis, the <title> tag is used twice. Apparently once in the partial head.html (as part of the pulled in software) and then again it is added here:

This causes an error in html validation. The code of this line is already incorporated into the head.html partial as found here: https://github.com/google/docsy/blob/8b786354829536454688df1e63b9cad792f68562/layouts/partials/head.html#L13

Removal from baseof.html would resolve that html validation error.

Don't have time to work it just yet, but I was thinking this should be worded so we don't have to come back every 30 days to edit the file due to a PHP or MySQL change.

We are currently recommending PHP 7.0 with an EOL of over a year ago.

A healthy balance between providing information and providing a link to current information is always best IMHO

Would you please update

https://docs.zen-cart.com/dev/code/notifiers/

and give that article a scrub and improve the examples? Thank you!

title and description are two fields in a page's front matter -the block at the top of the file.

Many pages have a description which is just a restatements of the title. As you are changing a file, please try to improve this by using other keywords from the file, to help people scanning the category page determine if this article is the one they want.

• Users (top level)
• First Steps
• New User Topics
• About
• Admin System
• Customizing your Site
• EZ-Pages
• Email
• Images
• Installing
• Localization
• Locations
• Miscellaneous
• Order Total
• Orders
• Payment
• Performance
• Plugins
• Products
• Running
• Security
• Shipping
• Sideboxes
• Template System
• Troubleshooting
• Upgrading
• Zen Cart Forum

This is already provided in Zen Cart versions 1.3.9+, so I think we can simplify this file by removing this step.

@drbyte agreed?

I would like to know how i would add sanitisation for a field that I add to say product details. So i add a field called product location which i want to be SIMPLE_ALPHANUM_PLUS.
should I create a file in /admin/includes/extra_datafiles/ say called product_details.php
and include the code.
$sanitizer = AdminRequestSanitizer::getInstance();
$group = array(
'id' => array('sanitizerType' => 'SIMPLE_ALPHANUM_PLUS', 'method' => 'both', 'pages' => array('products_details'), 'params' => array()),
);
$sanitizer->addComplexSanitization($group);

is it really that simple?
I assume that I would also have to include some validation in the updateproduct module etc. or is it ok to just assume that the sanitiser has done the job?

I have also added fields into shipping/and packing gID=7 at the moment they contain html and are altered to < etc so i update via database. but was wondering if this routine could be used in the future versions of zen cart to do the sanitisation?

https://github.com/zencart/documentation/blob/master/content/dev/code/creating_menu.md

item #4 has nothing to do with creating an admin menu item. creating a new tool, yes, but not creating a new admin menu item.

in addition, it seems like the notes is a second way to install a menu; and not really notes on installing. i think less is more, and i'm not sure if there is a page on creating a tool (which this pages has a lot of), and this page which, IMO should be ONLY about getting a menu item onto one of the menus.

Not an issue, just a thought for all to ponder in Item B, Upload the Zen Cart fileset to your webserver.

With the continuing problem of FTP failures from slow or intermittent connections, what we tell folks (especially for upgrading) is to FTP the fileset zip. Then, use your cPanel file manager to unzip the file, change the folder name from zen-cart-v1.5.6c-#### to test, store, tryout, whatever....

Regardless whether installing or upgrading, the danger of bad FTP is gone. It's certainly faster to work on the server than over FTP. Initial site setup can be done without prying eyes. And, when ready for prime time, either a 301 or a move to the root.

To me, the move to the root is "safer" than extracting the files and then uploading.

To date, we've not experienced problems with this method and we have a few out there that are "challenged".

I can see both sides, but I'm kinda 70/30 toward the zip upload.

Thoughts?

https://github.com/zencart/documentation/blob/master/content/user/upgrading/detailed_upgrading.md

Are we not doing the folks a grave injustice by sending them into the "what did I use before" jungle rather than just load and add the current mods they might need?

Working in spite of a dead desktop or I would have submitted a change to this already. But, I have personally seen the horror created by trying to use what was there before. I wish there were some way to just use products/customers/orders from a db on upgrade. The leftover/half-deleted/incorrectly upgraded files from the past are stifling.

Plus, 146 mods have been touched since the release of 1.5.6c. Touched, in some cases, includes multiple upgrades. The 146 is just the number of mods created since 1.5.6c. It does not include how many times thee mod has been updated.

With the inclusion of several prior-mods, things can get dicey. Zen non captcha was just one of the carryovers that took us off track with an upgrade from an original 1.5.0 to 1.5.6c that we upgraded to 1.5.7 for beta test. Admittedly ZNC was small but, add five or so of those and things get squirrelly. One of them was the reason for taking so long on the Whoops error.

Am I completely off-base with suggesting that the store owner just load a test site, add mods (Checked for currency), products, and move on? I know that's somewhat simplistic but, I hope you get my reasoning.

https://docs.zen-cart.com/user/troubleshooting/reset_admin_password/

Does not address password reset for versions of Zen Cart pre-1.5.x, meanwhile there are still those upgrading from those pre-1.5.x versions that no longer appear to have access to the admin password reset option. A previous FAQ link: http://tutorials.zen-cart.com/index.php?article=2 found at: https://www.zen-cart.com/content.php?126-i-cant-login-to-the-admin-after-installing-zen-cart points to the root of the docs site...

But then, a FAQ that I have linked (and am not providing here as I expect it too will get redirected and made unavailable without an adequate replacement) still works and DOES still have the necessary information to accomplish the desired task.

This is not meant to address the new encapsulated plugins.
However changes like
zencart/zencart#3624
may break some current plugins.

See https://github.com/zencart/zencart/pull/3373/files
and https://github.com/zencart/zencart/pull/3597/files

I'd like to run the Notifiers Report

https://github.com/lat9/notifier_report

at release time and post the file to the docs area, but I'd need the file to be markdown - can you output a markdown file for use by the docs? Doesn't have to be fancy.

https://github.com/zencart/documentation/blob/master/content/user/new_user_topics/new_misc.md

If left blank (undefined or ''), both the Congratulations (h1) and Welcome (h2) defines will cause an Accessibility error as the system still displays the tags but, as empty.

Until we can come up with a way for the store to ignore the two if they are undefined, perhaps add a NOTE: just before the "Save" statement.

Something like:

NOTE: Leaving this define blank ('') will result in an Accessibility validation error.

https://github.com/zencart/documentation/blob/master/content/dev/plugins/upgrading_to_1.5.md

Scott, I'm wondering: does this page fit best here? Or should it be with the other docs related to "release-specific considerations"?

I'm in the process of creating an order_total_modules.md and have come across a conundrum that is slowing me down.

Each of the order_total modules includes a function named pre_confirmation_check that is (to my old eyes) never called! My read on the pre_confirmation_check method is that it's totally (pun kind of intended) handled by the order_total class file.

My current thought is to document the fact that many of the order_total modules include this unused method and leave it at that. There are, additionally, some order-total simplifications that can occur!

Further to #218

• update user/products/download_delivery_methods with specifics on using AWS.
• cross link this content from brief discussion in content/user/products/downloadable.md

I've made a start:
https://github.com/torvista/Zen_Cart-PayPal_Sandbox_setup

Please flesh it out. I'm pretty green on PayPal.

http://docs.zen-cart.com/Contributing/main/github_workflow

Does not discuss the needed commands (submodule init, submodule update).

Need this content
https://www.zen-cart.com/wiki/index.php/Languages

https://github.com/zencart/documentation/blob/master/content/dev/plugins/encapsulated_plugins/manifests.md
"PluginId
The id number assigned by the Zen Cart forum site when submitting the plugin for review. e.g. https://www.zen-cart.com/downloads.php?do=file&id=1583 This is used to do call home checking for new versions"

The first time you submit a plugin you will not know the PluginId. Therefore is it ok to leave it blank(or assign a default no check value 0 maybe) or will you have to submit the plugin. get the id when assigned and resubmit the plugin with the id filled?

I am surprised to see v1.5.6 still using simple 6 character passwords for customer reset passwords, which most customers will not change.

Even Zen-cart's own documentation recommends long complex passwords, so why are your Password Resets not adhering to Zen-Cart's own recommendations?
Plus customers are not forced to choose a new password after the reset email is used.

Please at least allow Admins to control password length + complexity requirements for customers to remain PCI Compliant.

After all, our customers save their credit card info so a hacker could easily guess their 6-character password, hack into customer's account, buy merchandise and change the shipping addresses to himself. Not cool!

Customer passwords should be just as strict as admin passwords

Is it not time to starting talking about template_default as what it really is versus a viable template to be used for a store?

IMHO, template_basefiles, master_templatefiles, or something similar would stop a lot of confusion for new users.

Since 1.5.5 and the inclusion of responsive_classic as the true "default", I see constant confusion as to which template goes where, what files need to be where, etc.

As this doc states, template_default is the master set of template files -- Don't touch. Then, we are told that ZC comes with two other templates. Again, confusing.

Under Can I use template_default?, it's second paragraph even implies that template_default can be reached in the Tools >> Template Selection option. This is not an option as template_default
does not appear a a possible choice in Template Selection.

And, "pedagogic"?!? That will certainly drive some learning as folks drastically Google to see what this new command does in PHP or CSS. ;-)

I can already here the cries of "This is going to screw up sooo many mods." But, aren't we supposed to put overrides elsewhere in the first place?

mod, mods, modders and other variants of the word are slang that isn't part of actual Zen Cart code.

The term should be changed to something descriptive such as "your own customizations" or "installed addons" or "installed contributions" or "plugin" or "plugin author" depending on context. Each case will be unique.

https://github.com/zencart/zencart/pull/3597/files

scott,
i think this page should not be dug in as far as it is. at a minimum, i think it should at least be on the all time favorite list. i refer to it constantly (mostly because i can not remember anything), and it would be nice if i did not have to dig to find it all the time.

just my thoughts.

These docs https://docs.zen-cart.com/dev/zcgo/ are now deprecated.
With the introduction of Laravel, Zcgo is redundant in favour of Artisan.

I've already converted the make:defines (for creating array language files) to Artisan

Will up date this soon to replace with a section regarding Laravel integration

Hoping forum user RixStix will do it, otherwise I will.

https://www.zen-cart.com/showthread.php?226898-Login-as-customer

Start with 1.5.7 and then touch on pre-1.5.7 methods (ALAC, Master Password, EMP).