Search the Community

Hi All, Greetings of the day. The prestashop addon helps to add automatic schema markup microdata JSON-LD about products, business details, reviews, location, social pages, and many more to show google rich snippets in search results and helps in SEO. Automatic Facebook open graph and Twitter card tags on all pages. Testing using online tools. Supports other ratings and related software like Yotpo, Products Comments, Verified Reviews, TrustPilot, TrustMate, TrustedShop, and all other software for automatic integration of reviews and rating counts. Automatic schema markup microdata in JSON format on all pages. Helps to fix issues in Google search console and other webmaster tools. All valid schema markups in Google schema testing tools. Testing using online tools. All valid schema markups in Google schema testing tools and search console.Lifetime support and updates in the modules. Breadcrumblist, LocalBusiness, WebPage, WebSite, Organization, Products Page, offers, ratings, category products, logos schema markup added Automatic Facebook and Twitter metadata added on all pages. Google search works hard to understand the content of a page. We can help by providing explicit clues about the meaning of a page to Google by including structured data on the page. Structured data is a standardized format for providing information about a page and classifying the page Structured data refers to information with a high degree of organization, such that inclusion in a relational database is seamless and readily searchable by simple, straightforward search engine algorithms or other search operations. Structured data is added directly to a page's HTML markup. Search engines use structured data to generate rich snippets, which are small pieces of information that will then appear in search results. Rich Snippets is the term used to describe structured data markup that site operators can add to their existing HTML, which in turn allows search engines to better understand what information is contained on each web page. JSON-LD is the format that Google regularly recommends. It helps in online store quality in the eyes of Google. Its important SEO understand its usefulness and impact. In 2009, Google further refined snippet results by introducing “rich snippets.” Rich snippets serve as a “sneak preview” for listings on the SERP and can supplement search query results with more detailed information. This additional information can help searchers gauge which website might best answer their search query. - Higher Chances of Ranking on SERPs - Better Click through Rates - Better Marketing Opportunity - More Qualified Leads - More Credibility - Reduce expenses - Increase sales - Improve customer service and loyalty - Customer convenience - Competitive advantages - Expand market reach - Proactive outreach - Reports and analytics - Real-Time Convenience to Customers - Cost-Efficient - Stand out Among Competitors - Eye-catching results => drawing a search user’s attention from your competitors’ listings to your own result. - Potential CTR increases => Possibly increasing click-through rates and lowering the chance of the user ‘bouncing’ as they see more information about the page before clicking through (there is also the potential to deter users if the additional rich snippets information shows something they were not looking for). - Providing ‘quality’ results => offering results that could match the user’s intent more closely. On the downside, if the informational benefit of the rich snippet satisfies the user's search query, it might eliminate the need to click through for further engagement. - Develop Deeper Customer Relationships - Increase in Conversions and Average Order Values Features: Helps in Search Engine Optimization. Boost Your SEO by Using Schema Markup. Automatic Facebook open graph and Twitter card tags on all pages. Testing using online tools. Automatic schema markup microdata in JSON-LD format on all pages. Automatic ratings and review integration. Supports other ratings and related software like Yotpo, Products Comments, Verified Reviews, TrustPilot, TrustMate, TrustedShop, and all other software for automatic integration of reviews and ratings count. Helps to show rich snippets in search results using stars, prices, quantities, and other details. Helps to fix issues in Google search console and other webmaster tools. All valid schema markups in Google schema testing tools and search console. Lifetime support and updates in the modules. Breadcrumblist, LocalBusiness, WebPage, WebSite, Organization, Products Page, offers, ratings, category products, logos schema markup added, Automatic Facebook and Twitter metadata added on all pages. Helps to improve visibility on social networks Helps to optimize natural search (SEO) on all search engines Automatic schema information for all products in front-office (JSON-LD format ) and back-office. Automatic BreadcrumbList schema generation in front-office for all products. Helps in improvement in ranking in all search engines. It helps in an increase in web traffic. Helps to get targeted traffic and related store products and services. Provide greater information to search engines to improve their understanding of your business and of the content on your website. It can act as an authentication for a business address if it matches the Google Business Listing, in doing so improves local SEO. Implementing rich snippets can have a huge impact on how your pages perform in the search engines. It helps to increase visibility in the search results It helps to improve click-through rates and attract more targeted traffic. Fully responsive 100%. SEO friendly. Support all browsers: Firefox, Chrome, IE, Safari, etc. Lightweight. (Smaller file size which loads faster.) Increase sales, conversion rates, and product promotions. Maintain existing customers & Attract new customers. Lower marketing expenses, exposure to potential customers, reach targeted audiences. Compatible with PrestaShop 1.5.x,1.6.x,1.7.x and 8.0 Multiple browsers compatibility(IE, Firefox, Opera, Safari, Chrome, and Edge). Mobile, Tablet and all device compatible. Multi-language and Multi Store compatible. Module works without doing any change in existing files on PrestaShop store versions. 24*7 Support Good Documentation Installation : Step 1: Upload module zip file from the back-office Module & Services menu tab. Module Manager area using the upload button. After the successful installation module menu, the link will appear in the left menu or top menu in back-office more area. Step 2: Install the module using the install button. Step 3: Visit module management page from the back-office "More" area (section) in the left menu in the back-office. Step 4: The module installation process is very easy, how module configuration works can be seen in the demo instance. Step 5: Please visit our demo instance for module configuration and usage demo. Step 6: Please watch the module installation, configuration, and how-to-use video on our YouTube channel. - Module works without making any change in the existing PrestaShop file so that existing customization and theme change do not affect. - We provide free technical and feature support in installation, configuration, as well as access to updates available for this product. - Free support on installation, configuration, and customization as per store requirements, for example, new hook addition on your store What's New in Version The enhancements for showing data on products,home page,currencies of different countries(Europe,North,South America,Asia),Breadcrumblist schema,text-area,SKU,MPN,discounted product price valid dates new fields added,changes as per google documentation.Automatic schema generation on all product pages in front-office (multi-languages) and back-office module pages.Configure option for all social media links.Automatic Reviews integration with other modules.Web Page,Organization,Local Business & Search Schema. Supports versions 1.5,1.6 and 1.7. Added schema on categories pages. Yotpo ,TrustMate and other software plugins review integration with my module. For a list of modules on PrestaShop Addons Marketplace. https://addons.prestashop.com/en/2_community-developer?contributor=301729 Please feel free to contact me for any support in installation, configuration, and customization in the module as per your store requirements. BUY USEFUL PRESTASHOP ADDONS FOR ONLINE STORES https://www.presta-addons-modules.com/en/ Front-office Demo URL => https://www.hrms-systems.com/presta-addons/en/ Back-office Demo URL => https://www.hrms-systems.com/presta-addons/admin619j6kpbb/index.php For a demo on version 1.6.x visit the below links Front-office Demo URL => https://www.hrms-systems.com/presta-apps/en/ Back-office Demo URL => https://www.hrms-systems.com/presta-apps/admin539fyipwq/index.php We have default schema information added by the PrestaShop theme or any other theme. It has many missing tags that show errors and warnings in the schema testing tool and search console. This work requires FTP details of the theme to do customization in theme tpl files with extra customization work of 30 euro. I had solved the issue on many websites in a few hours using their FTP details. I have tested pages after my work using the Google testing tool (https://search.google.com/structured-data/testing-tool) and https://search.google.com/test/rich-results?utm_campaign=sdtt&utm_medium=url Attached screenshots from the search console having zero error or warning message. YouTube Demo Link

Hello, I am trying to get blank schema for products resource and I get this error: [PHP Warning #2] Illegal string offset 'required' (.../classes/webservice/WebserviceOutputBuilder.php, line 711) Does anyone please know how to fix it? I am using prestashop 1.7.1.0 Thanks in advance.

Hi everyone, I am sandbox upgrading a copy of my live prestashop website in MAMP (free) following the iteration: - my website is a 1.6.1.3 - I perform an update of the stated 1.6.1.3 to a 1.6.1.24 with 1-click update and everything goes smooth, than I change MAMP from php 5.6.40 to 7.1.33 while uninstalling and deleting (in this order) all non native modules and themes except revws and payplug - I fresh install, in a different htdocs directory and in a different database, a 1.6.1.24 and I copy inside modules revws and payplug, the img folder and the setting file - I delete the 1.6.1.3 updated to 1.6.1.24 directory and the fresh install 1.6.1.24 database and connect the 1.6.1.24 fresh install to the 1.6.1.3 updated to 1.6.1.24 database and I modify the fresh install 1.6.1.24 directory to match the updated one that has been deleted - So I have a fresh install of prestashop connected to my previous historical complete database - In all of this process I kept non native module and overrides deactivated and performed multiple database checkout with module prestashop cleaner 1.8 and reverted to official theme, so a very "vanilla" situation. At this point, I tested all the functions of local website I find myself with and everything seems to go fine, no errors while using debug mode, so I feel comfortable in using 1-click module to update to PS 1.7.7.4. - I put the zip in the download folder and proceed with the update. Everything goes smooth in the files update (all green), but when the process goes to the database, I find myself with an error and a barely accessible back office, with front-office, and back office orders, customers and setting unaccessible due to too many redirects. Here you are the database update situation and errors: Updating database schema... Executing: CREATE TABLE ps_translation (id_translation INT AUTO_INCREMENT NOT NULL, id_lang INT NOT NULL, `key` TEXT NOT NULL COLLATE utf8_bin, translation TEXT NOT NULL, domain VARCHAR(80) NOT NULL, theme VARCHAR(32) DEFAULT NULL, INDEX IDX_ADEBEB36BA299860 (id_lang), INDEX `key` (domain), PRIMARY KEY(id_translation)) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci ENGINE = InnoDB Executing: CREATE TABLE ps_module_history (id INT AUTO_INCREMENT NOT NULL, id_employee INT NOT NULL, id_module INT NOT NULL, date_add DATETIME NOT NULL, date_upd DATETIME NOT NULL, PRIMARY KEY(id)) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci ENGINE = InnoDB Executing: CREATE TABLE ps_admin_filter (id INT AUTO_INCREMENT NOT NULL, employee INT NOT NULL, shop INT NOT NULL, controller VARCHAR(60) NOT NULL, action VARCHAR(100) NOT NULL, filter LONGTEXT NOT NULL, filter_id VARCHAR(191) NOT NULL, UNIQUE INDEX admin_filter_search_id_idx (employee, shop, controller, action, filter_id), PRIMARY KEY(id)) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci ENGINE = InnoDB Executing: DROP INDEX lang_iso_code ON ps_lang Executing: ALTER TABLE ps_lang CHANGE active active TINYINT(1) NOT NULL DEFAULT '0' , CHANGE iso_code iso_code VARCHAR(2) NOT NULL, CHANGE language_code language_code VARCHAR(5) NOT NULL, CHANGE date_format_lite date_format_lite VARCHAR(32) NOT NULL DEFAULT 'Y-m-d' , CHANGE date_format_full date_format_full VARCHAR(32) NOT NULL DEFAULT 'Y-m-d H:i:s' , CHANGE is_rtl is_rtl TINYINT(1) NOT NULL DEFAULT '0' Executing: CREATE INDEX IDX_2F43BFC7BA299860 ON ps_lang_shop (id_lang) Executing: ALTER TABLE ps_lang_shop RENAME INDEX id_shop TO IDX_2F43BFC7274A50A0 Executing: DROP INDEX id_lang ON ps_attribute_lang Executing: CREATE INDEX IDX_3ABE46A77A4F53DC ON ps_attribute_lang (id_attribute) Executing: CREATE INDEX IDX_3ABE46A7BA299860 ON ps_attribute_lang (id_lang) Executing: DROP INDEX deleted ON ps_shop_group Executing: ALTER TABLE ps_shop_group CHANGE active active TINYINT(1) NOT NULL DEFAULT '1' , CHANGE deleted deleted TINYINT(1) NOT NULL DEFAULT '0' Executing: DROP INDEX id_parent ON ps_tab Executing: DROP INDEX class_name ON ps_tab Executing: ALTER TABLE ps_tab ADD route_name VARCHAR(256) DEFAULT NULL, CHANGE position position INT NOT NULL, CHANGE active active TINYINT(1) NOT NULL DEFAULT '1' , CHANGE hide_host_mode hide_host_mode TINYINT(1) NOT NULL DEFAULT '0' , CHANGE icon icon VARCHAR(32) DEFAULT '' Executing: DROP INDEX id_shop_group ON ps_shop Executing: DROP INDEX id_category ON ps_shop Executing: ALTER TABLE ps_shop CHANGE id_category id_category INT NOT NULL DEFAULT '1' , CHANGE theme_name theme_name VARCHAR(255) NOT NULL, CHANGE active active TINYINT(1) NOT NULL DEFAULT '1' , CHANGE deleted deleted TINYINT(1) NOT NULL DEFAULT '0' Executing: CREATE INDEX IDX_CBDFBB9EF5C9E40 ON ps_shop (id_shop_group) Executing: ALTER TABLE ps_attribute CHANGE color color VARCHAR(32) NOT NULL, CHANGE position position INT NOT NULL DEFAULT '0' 01:24:42 ERROR [console] Error thrown while running command "prestashop:schema:update-without-foreign --env=prod". Message: "An exception occurred while executing 'ALTER TABLE ps_attribute CHANGE color color VARCHAR(32) NOT NULL, CHANGE position position INT NOT NULL DEFAULT '0' ': SQLSTATE[01000]: Warning: 1265 Data truncated for column 'color' at row 20" ["exception" => Doctrine\DBAL\Exception\DriverException { …},"command" => "prestashop:schema:update-without-foreign --env=prod","message" => """ An exception occurred while executing 'ALTER TABLE ps_attribute CHANGE color color VARCHAR(32) NOT NULL, CHANGE position position INT NOT NULL DEFAULT '0' ':\n \n SQLSTATE[01000]: Warning: 1265 Data truncated for column 'color' at row 20 """] In AbstractMySQLDriver.php line 106: An exception occurred while executing 'ALTER TABLE ps_attribute CHANGE colo r color VARCHAR(32) NOT NULL, CHANGE position position INT NOT NULL DEFAULT '0' ': SQLSTATE[01000]: Warning: 1265 Data truncated for column 'color' at row 20 In PDOConnection.php line 90: SQLSTATE[01000]: Warning: 1265 Data truncated for column 'color' at row 20 In PDOConnection.php line 88: SQLSTATE[01000]: Warning: 1265 Data truncated for column 'color' at row 20 prestashop:schema:update-without-foreign [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-e|--env ENV] [--no-debug] [--id_shop [ID_SHOP]] [--id_shop_group [ID_SHOP_GROUP]] [--] Do you have any solution to suggest? How do I address which tables are provoking the issue in order to correct them before proceeding with the 1.7.7.4 update? Thanks a lot for any suggestion provided. The following are the specifications of MAMP at the time of the error: PHP: 7.1.33 max_execution_time30000 max_file_uploads20 max_input_nesting_level64 max_input_time60000 max_input_vars10000 memory_limit1024M post_max_size256M Web server: Apache [SOLVED] After posting the problem also on stackoverflow I was made to notice that the error message clearly referred to a field regulated in the database by a VARCHAR of up to 32 characters including spaces which appeared to be populated in excess. Found the field, reduced the content from 35 to 29 characters and this error was resolved, allowing me to reach completion of the update. In any case, given the excess of errors from previous installation (database and prestashop are carried out, without reset, since 2013), I connected the database updated to 1.7 to a fresh install 1.7. I currently have permissions problems on this new database, but this specific issue has been fixed.

Hello, I am trying to add a Schema.php file in the head of Prestashop. the Schema.php file contains a if statement. basically when a certain URL is loaded then the schema is triggered. if( $_SERVER['REQUEST_URI'] == '/customizable-car.html' ) My knowledge of prestashop is quite frankly a bit dangerous and would appreciate it if someone could direct me to where I can import the schema.php file so that it does its function properly.

Hi, I need to calculate the stock balance on a particular date, ie. roll back the stock balance from 'today' and determine the balance on a past date. My error for not doing or keeping a backup on that date! I dont need anything flash, a simple flat file is all I need. ie. I dont need PS to be working effective on this historical date. Just need the stock balance data... I plan to run a simple sql script to perform the calculation. In this regard, my query relates to the database schema for PS1.6 to make sure I determine it correctly. It looks like I can achieve this through the ps_stock and the ps_stock_mvt tables. I am guessing that if I start with the balance from the ps_stock>physical_quantity field and then adjust it for all of the movt records in my date rate using the ps_stock_mvt>physical_quantity field. Any advice in this regard would be appreciated. Thanks Mark

Hi guys. I am using prestashop version 1.7.6.3 I use the default classic theme I am also using google google search console and structured data testing tool on my product pages. Every product in my store are marked as an error: "Either "offers", "review", or "aggregateRating" should be specified" My question is, what course of action needs to be taken to correct these product issues. Which files do i need to be looking at and how is it best to apply corrections. Also to note in the field "name" there is a warning "(The property price is not recognized by Google for an object of type Product.)" Kind regards

Hola estoy creando una aplicacion que accede a mi prestashop no tengo problema en cojer la informacion del producto ( por ejemplo ) obteniendo los valores de los campos, lo que me interesa es tener la descripcion del campo es decir que stock por ejemplo me de la descripcion de este en el lenguaje de la tienda que tengo definido, es decir stock = estoc , la informacion que sale en la ficha en mi tienda prestashop. no lo encuentro por ningun lado, a ver si me podeis hechar un cable por favor. Saludos

Bonjour à tous, Salutations du jour. Cet addon permet d'ajouter des données structurées sur les détails de l'entreprise, les heures d'ouverture, les avis, l'emplacement et les pages sociales, etc. pour afficher un extrait riche dans les résultats de recherche et aider au référencement. La recherche Google travaille dur pour comprendre le contenu d'une page. Nous pouvons vous aider en fournissant des indices explicites sur la signification d'une page à Google en incluant des données structurées sur la page. Les données structurées sont un format normalisé pour fournir des informations sur une page et classer la page Les données structurées se réfèrent à des informations avec un haut degré d'organisation, de sorte que l'inclusion dans une base de données relationnelle est transparente et facilement consultable par des algorithmes de moteur de recherche simples et directs ou d'autres opérations de recherche. Les données structurées sont ajoutées directement au balisage HTML d'une page. Les moteurs de recherche utilisent des données structurées pour générer des extraits riches, qui sont de petites informations qui apparaîtront ensuite dans les résultats de recherche. Rich Snippets est le terme utilisé pour décrire le balisage de données structurées que les opérateurs de sites peuvent ajouter à leur code HTML existant, ce qui permet aux moteurs de recherche de mieux comprendre les informations contenues sur chaque page Web. JSON-LD est le format que Google recommande régulièrement. Il aide à la qualité de la boutique en ligne aux yeux de Google. Son référencement important comprend son utilité et son impact. En 2009, Google a affiné les résultats des extraits de code en introduisant des «extraits enrichis». Les extraits enrichis servent d'aperçu pour les listes sur le SERP et peuvent compléter les résultats des requêtes de recherche avec des informations plus détaillées. Ces informations supplémentaires peuvent aider les chercheurs à évaluer le site Web qui répond le mieux à leur requête de recherche. - Meilleures chances de classement sur les SERPs - Meilleurs taux de clics - Meilleure opportunité de marketing - Plus de prospects qualifiés - Plus de crédibilité - Réduisez les dépenses - Augmenter les ventes - Améliorez le service client et la fidélité - Confort client - Avantages concurrentiels - Étendre la portée du marché - Sensibilisation proactive - Rapports et analyses - Commodité en temps réel pour les clients - Rentable - Se démarquer parmi les concurrents - Des résultats accrocheurs => en attirant l'attention d'un internaute sur les listes de vos concurrents vers vos propres résultats. - Le CTR potentiel augmente => Peut-être en augmentant les taux de clics et en réduisant les chances que l'utilisateur "rebondisse" lorsqu'il voit plus d'informations sur la page avant de cliquer (il y a aussi le potentiel de dissuader les utilisateurs si les informations supplémentaires sur les extraits riches montrent quelque chose ils ne cherchaient pas). - Fournir des résultats de «qualité» => offrir des résultats qui pourraient mieux correspondre à l'intention de l'utilisateur. En revanche, si l'avantage informationnel de l'extrait enrichi satisfait la requête de recherche de l'utilisateur, il peut éliminer la nécessité de cliquer pour un engagement plus poussé. - Développer des relations clients plus approfondies - Augmentation des conversions et des valeurs moyennes des commandes Fonctionnalités: - Aide à l'optimisation des moteurs de recherche. Boostez votre référencement en utilisant le balisage de schéma. - Aide à l'amélioration du classement dans tous les moteurs de recherche. - Il contribue à une augmentation du trafic Web. - Aide à obtenir un trafic ciblé et des produits et services liés aux magasins. - Fournir une plus grande information aux moteurs de recherche pour améliorer leur compréhension de votre entreprise et du contenu de votre site Web. - Il peut agir comme une authentification pour une adresse commerciale si elle correspond au - Google Business Listing améliore ainsi le référencement local. - La mise en œuvre d'extraits enrichis peut avoir un impact énorme sur les performances de vos pages dans les moteurs de recherche. - Il contribue à augmenter la visibilité dans les résultats de recherche - Il contribue à améliorer les taux de clics et à attirer un trafic plus ciblé. - 100% réactif. - SEO convivial. - Prise en charge de tous les navigateurs: Firefox, Chrome, IE, Safari, etc. - Poids léger. (Taille de fichier plus petite qui se charge plus rapidement.) - Augmentez les ventes, les taux de conversion et les promotions de produits. - Maintenir les clients existants et attirer de nouveaux clients. - Baisse des dépenses marketing, exposition aux clients potentiels, atteindre des publics ciblés. - Compatible avec PrestaShop 1.5, 1.6 et 1.7. - Compatibilité de plusieurs navigateurs (IE, Firefox, Opera, Safari, Chrome et Edge). - Mobile, tablette et tous les appareils compatibles. - Compatible multilingue et multi-magasins. - Le module fonctionne sans faire de changement dans les fichiers existants sur les versions de la boutique PrestaShop. - Support 24 * 7 - Bonne documentation Installation: Étape 1: Téléchargez le fichier zip du module à partir de l'onglet de menu Module et services de back-office. Zone du gestionnaire de modules à l'aide du bouton de téléchargement. Après le menu du module d'installation réussi, le lien apparaîtra dans le menu de gauche ou le menu supérieur dans la zone back-office plus. Étape 2: installez le module à l'aide du bouton d'installation. Étape 3: Visitez la page de gestion des modules depuis la zone "Plus" du back-office (section) dans le menu de gauche du back-office. Étape 4: Le processus d'installation du module est très simple, le fonctionnement de la configuration du module peut être vu dans l'instance de démonstration. Étape 5: veuillez visiter notre instance de démonstration pour la configuration du module et la démonstration d'utilisation. - Le module fonctionne sans apporter de modification dans le fichier PrestaShop existant afin que la personnalisation existante et le changement de thème n'affectent pas. - Nous fournissons un support technique et fonctionnel gratuit lors de l'installation, de la configuration, ainsi que l'accès aux mises à jour disponibles pour ce produit. - Support gratuit sur l'installation, la configuration et la personnalisation selon les exigences du magasin, par exemple, l'ajout de nouveaux crochets sur votre magasin Les améliorations pour l'affichage des données sur les produits sélectionnés, l'option de page d'accueil uniquement, les devises de différents pays (Europe, Amérique du Nord, Amérique du Sud, Asie, Russie et Moyen-Orient), schéma Breadcrumblist, zone de texte, SKU, MPN, prix du produit à prix réduit dates valides ajout de nouveaux champs, modifications selon la documentation google des données structurées et rich snippet. Génération automatique de schémas sur toutes les pages produits de la page du module front-office et back-office pour une édition facile. Configurez l'option pour les liens sociaux communs et les prix réduits. Commentaires automatiques et décompte des étoiles à partir du module de commentaires sur les produits. Notes ajoutées Intégration avec les commentaires des produits, le module lgcommets et d'autres modules. Acheter un module sur le marché des addons en utilisant l'URL ci-dessous https://addons.prestashop.com/en/seo-natural-search-engine-optimization/31857-seo-structured-data-schema-markup-rich-snippet.html Pour une liste des modules sur PrestaShop Addons Marketplace. https://addons.prestashop.com/en/2_community-developer?contributor=301729 N'hésitez pas à me contacter pour toute assistance concernant l'installation, la configuration et la personnalisation du module selon les exigences de votre magasin. ACHETER DES ADDONS PRESTASHOP UTILES POUR LES MAGASINS EN LIGNE https://www.presta-addons-modules.com/en/ URL de démonstration du front-office => https://www.hrms-systems.com/presta-addons/en/ URL de démonstration du back-office => https://www.hrms-systems.com/presta-addons/admin619j6kpbb/index.php Nous avons des informations de schéma par défaut ajoutées par le thème PrestaShop ou tout autre thème. Il contient de nombreuses balises manquantes qui affichent des erreurs et des avertissements dans l'outil de test de schéma et la console de recherche. Ce travail nécessite des détails FTP du thème pour effectuer la personnalisation dans des fichiers tpl de thème avec un travail de personnalisation supplémentaire de 30 euros. J'avais résolu le problème sur de nombreux sites Web en quelques heures en utilisant leurs détails FTP. J'ai testé des pages après mon travail à l'aide de l'outil de test Google (https://search.google.com/structured-data/testing-tool) Captures d'écran jointes de la console de recherche n'ayant aucun message d'erreur ou d'avertissement. Vidéo de démonstration sur Youtube

I am getting a lot of errors on webmaster tools regarding "missing name and name required". I figure it out that its probably due to "itemprop= url" instead of "itemprop=name" under the item-info/item-title tags. I can also see errors getting removed as i change url to name in itemprop but when i do the same through c-panel in product-list.tpl, i see no change in errors. How do i fix this?? This is the issue in default structured data- This is where i tried to fix this through c-panel in product-list.tpl -

Hello, in Google webmaster tools, I have the same error (missing price) for every product page. The main product price and currency schema configuration is fine and doesn't lead to errors. But, at the bottom of product page I have the module "Related products" (/modules/productscategory) and it returns missing price error. The code is something like this: <div itemprop="offers" itemscope="" itemtype="http://schema.org/Offer" class="content_price"> <span itemprop="price" class="price product-price"> CHF 100.00 </span> <meta itemprop="priceCurrency" content="0"> </div> As I understand it, we have priceCurrency error: content should be ="CHF" and not "0". Did anybody face the same issue? Thank you

I threw this topic together to get a consensus and brainstorm going on how to best change the structure of the default-bootstrap category.tpl microdata markup. I've been talking to the project lead who also works for google and a representative of goodrelations.org on this github issue. Nested Categories The problem I found puzzling is how to express nested categories and the products. Do commits to PrestaShop core theme and then respond to my github issue and ask them to review markup and integrate any of their recommendations. Not looking for any credit. Just others who understand the smarty variables involved and recreate the structure necessary so that everyone using bootstrap benefits from our open source collaboration. Your Mission If You So Choose Reply if you don't know what schema.org can do for rich snippets and structured data. Reply if you want to learn theme coding for structured data. Reply if you are the grand [spam-filter] of all things code. http://forge.prestashop.com/browse/PSCSX-5694 is the original issue tracker Goal Completion Let's shoot for final commit by 31 Oct 2015

Hi Folks, I'm trying to integrate a XSD/XML Schema into my prestashop but I can't seem to find a suitable module to assist with the installation and with my limited IT experience i'm unsure how to make the installation manually. Can someone please help? Would be truly grateful. Thanks, Justin.

Witam, Mam dość dziwny problem. Korzystam z modułu Google Rich Snippets + Product Ratings and Reviews, który używa znaczników data-vocabulary.org. Ma on dość ograniczone możliwości, to postanowiłem rozszerzyć pakiet o znaczniki schema.org i powstawiać do modułu, tym samym rozszerzając opis produktów, czy też samego sklepu. Nie chciałem aby wyświetlał się moduł w stopce, więc zamiast używać display:none (co nie jest zalecane), wyrzuciłem go poza margines. Sytuacja w narzędziach webmasterskich googla wygląda następująco: przy testowaniu znaczników również nie wywala błędu: i teoretycznie wszystko ładnie, w wyszukiwarce powinno się pokazywać, Problem w tym, że jednak się nie pokazuje. Jest zwykły wynik wyszukiwania. Tytuł strony, link, i opis. Nic więcej :/ co może być nie tak? czy to, że wywaliłem moduł po za margines, czy może to, ze wymieszałem znaczniki? a może gdzieś indziej błędu szukać?

Hi, i've necessity to manage multiple warehouse movements, but with actual webservice i can't do all action that i need, so i've started a new webservice, based on this resource: http://webkul.com/blog/how-to-add-new-tables-in-rest-api-of-prestashop/ I've created the service, but i've this error: This call to PrestaShop Web Services failed and returned an HTTP status of 400. That means: Bad Request. when i've checked the schema, i saw that the schema response is empty. Have you some suggestions on this problem? Thanks for your time. Best regards.

Hi, I am only new to crating a web site with Presta. I am not a computer programmer and I dont know too much with web sites however I am having a go. My first question is how do I change the schema of URL in presta shop. Please be specific as I have no idea! The second question is at the back office of presta shop I have this warning This is different from the domain name set in the "SEO & URLs" tab. If this is your main domain, please change it now. I have no idea what to write in the schema of URL tabs. Please could anyone help Regards Gillian

Bonjour, Je vous présente mon dernier module qui permet la gestion de "plans éclatés" sur les fiches produits ! Les principales fonctionnalités du module : Création de plans éclatés Ajout de zone de survol pour chaque élément du plan et association avec un produit Possibilité de personnalisé l'image au moment du survol Listing de tous les produits du plan Au survol du plan, le produit sous le curseur se met en avant dans le listing des produits. Au survol d'un produit de la liste des produits, le produit se met en avant sur l'image Ajout automatique d'un onglet "Plan éclaté" dans la fiche des produits contenus dans ce plan Multi-boutique Multilingue Ce module est particulièrement adapté aux pièces détachées Plus d'infos sur la page du module : http://www.smorillon.com/produits/32-plan-eclate-prestashop-153.html Démo du module sur la page suivante : http://demo.smorillon.com/multiple-cle/18-vis-1.html Bonne journée à tous.

I am trying to move my web site to any other web hosting firm. I coppy paste all folders to my new hosting account. Somehow at the final step when I am trying to import my database to new server via BigDump (Staggered MySQL Dump Importer v0.35b) I am reciving the message follow. I can not solvee it. Error at the line 21: CREATE DATABASE `information_schema` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci; Query: -- -- CREATE DATABASE `information_schema` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci MySQL: Access denied for user 'modancom_2'@'%' to database 'information_schema' Do you have any idea? Thanks

Hi all, i'm getting into the webservice thing and i've got some questions about the order of the actions i have to do. i have a new prestashop installation, i would like to populate it with products taken from a CSV that the client gave me. this csv has for each line, a PRODUCT COLOR, with all the quanitites of all the sizes, so for instance, i'll have: 1 awesome product name; 10 dark black;1;4;5;5;5;5;xs;s;m;l;xl;xxl;23.45 2 awesome product name; 11 white;3;5;1;1;1;1;xs;s;m;l;xl;xxl;23.45 3 awesome product name; 31 Pink;5;6;2;3;4;5;xs;s;m;l;xl;xxl;23.45 4 another product name; 31 Pink;1;1;2;6;4;4;xs;s;m;l;xl;xxl;21.00 5 third product name; 11 white;1;;;;;;U;;;;;;21.00 note that the last product is present in only a size, with a single color, and there is only one of them in stock. perfect, now i would like to understand the logic of what i'm going to do. the first thing to do is to get ALL the product characteristics? i mean, i should insert the various "product_option_values" as they have been called in the webservice thingy? so i will insert: 10 dark black xs s m l xl xxl 11 white 31 pink U which are all the characteristic used to make combinations in the file... then i have to insert each product, without combinations. So: awesome product name another product name third product name then, i have to make the combinations, and insert them, using the product_option_values ids and item ids, then finally, i send images, yes i've got them too... is that with some sense? or i'm getting all wrong?

Bonjour, Je souhaiterais ajouter plusieurs images dans les catégories. Autrement dit, j'ai une image qui représente la catégorie et une autre serait un schema. La disposition voulue de ces deux éléments fait qu'on ne peut pas les fusionner (on affiche du texte entre les deux image). J'ai déjà créé le champ pour charger une image (qui se charge correctement), là où je bloque c'est à l'endroit où cette image est traitée. Je ne trouve pas le fichier qui crée l'image à partir de celle temporaire, etc. Alors mes questions sont : Est-ce que le système est capable de charger plusieurs images pour une même catégories ou est-ce qu'il est bloqué sur une seule image ? Dans quel fichier est-ce que le traitement de l'image chargée est effectué ? J'ai essayé de trifouiller dans le fichier AdminCategories au niveau de la fonction postImage(), mais sans grand succès. Si quelqu'un pouvait m'aiguiller un peu. Merci.