Vicente Paul

Google will discover that automatically, but sending the URLs in the search console will be quicker...

Yes... have a look at this: https://www.ecoturismoecultura.com/br/?amp=1 The topic is here: https://www.prestashop.com/forums/topic/605735-accelerated-mobile-pages-amp-module-for-prestashop-16-soon-17/page-4?do=findComment&comment=2604846

The second issue was explained by the Google Search Console, see in attachment... Put in robots.txt: Allow: */themes/classic/assets/cache/*.css Allow: */themes/classic/assets/cache/*.js Allow: */themes/classic/assets/css/*.css Allow: */themes/classic/assets/js/*.js

The extra-spaces between the menu links, I already solved like this (in bold): /public_html/themes/classic/templates/cms/category.tpl {block name='page_content'} {block name='cms_sub_categories'} {if $sub_categories} <p>{l s='List of sub categories in %name%:' d='Shop.Theme' sprintf=['%name%' => $cms_category.name]}</p> <ul> {foreach from=$sub_categories item=sub_category} <li><a href="{$sub_category.link}">{$sub_category.name}</a></li> <span> </span> {/foreach} </ul> {/if} {/block} {block name='cms_sub_pages'} {if $cms_pages} <p>{l s='List of pages in %name%:' d='Shop.Theme' sprintf=['%name%' => $cms_category.name]}</p> <ul> {foreach from=$cms_pages item=cms_page} <li><a href="{$cms_page.link}">{$cms_page.meta_title}</a></li> <span> </span> {/foreach} </ul> {/if} {/block} {/block}

There is a big SEO issue with MENU CMS sub-categories links in mobile (see in the 2 atachments), because spaces between the CMS sub-categories links are too close. The problem is that as this is part of the menu, all pages are considered as non-mobile friendly!! The same problem occurs with the CMS Page links which are too close. => ANYBODY KNOWS HOW TO MODIFY THE CSS TO HAVE BIGGER SPACES BETWEEN THESES MENU LINKS? It also seems the Google bot cannot read the Menu css, because it shows the menu without any styling. Because it indent each link level, the Google bot also says that the content is wider that the screen size (which is not true).

Thanks for your help, horiatb! Actually I just succeed doing to "upgrade", reinstalling PS 1.7.1.2 from scratch, copy back the images and small modif. I made on the PS 1.7.1.0, using the PS 1.7.1.0 database with the latest patched PS 1.7.1.2 version. Everything seems ok! (I just needed re-doing some setup) You just need to update these 4 entries from the previous databas into .../public_html/app/config/parameters.php DB, USER, PWD, TABLE_PREFIX. Of course, it worked just because it was between 2 same minor PS 1.7.1.x versions (it will not work with 1.7.2.x). Anyway, I found the Prestashop releases/update process A SHAME, and will not upgrade anymore for the 5 coming years (already skipping the next major release), and never upgrade anymore with a major version newer than 10 month! There is ZERO support and compromise with Prestahop, and we are just losing time and energy...

Anybody knows if reinstalling PS 1.7.1.2 from scratch, copy back the images, and doing a full restore of the previous PS 1.7.1.0 database will work??

...even better: it deleted the autoupgrade and all subdirectories!!

Yes that updater seems corrupt, so I tried the latest test version of the updater, and it´s even worse!: - it doesn´t know about the 1.7.1.2 (just know about the the previous 1.7.1.1 version); - in manual mode, it even doesn´t find the .zip file which is there; Really painfull!

...even manually with prestashop.zip into adminxxx/autoupgrade/download/

Same problem trying to upgrade from PS 1.7.1.0 to 1.7.1.2 (it´s a shame!)

Thanks for trying to solve the problem Andrej, but I had already done that... I guess the 1-click module even don´t see the diference between PS 1.7.1.0 and 1.7.1.1, and so does nothing. What I will try is the following: as the PS 1.7.1.2 is going to be released now, I will do a last try... If it doesn´t work (after doing full directories and DB backups), I will reinstall PS 1.7.1.2 from scratch, copy back the images (and small modifications I made in .css and .php), and do a full restore of the previous PS 1.7.1.0 database to recover all my work, as a guess the database didn´t change between PS 1.7.1.0 and 1.7.1.2... What do you think about that?

Will it be possible to copy some files from the future PS 1.7.2 and paste them into PS 1.7.1.2 to get the "Improve readability on Classic theme #7681", without updating to PS 1.7.2? What are the files to copy to implement that in PS 1.7.1.2? (https://github.com/PrestaShop/PrestaShop/pull/7681)

PS 1.7.1.2 didn´t came as promised, seems PS 1.7.1.3 not exists anymore, no more due date for nothing (see https://github.com/PrestaShop/PrestaShop/milestones). Anybody knows what is happening??

Thanks!