prestashop / example-modules Goto Github PK

Hello,

I am trying to use the ActionProductFormBuilderModifier hook from the demoproductform module, but I don't see the "Demo custom field" field in the Description tab. I do see the new module tab in the Product page, but not the new field from the ActionProductFormBuilderModifier. The "New product page" feature is enabled.

Does someone know how to fix it? Is it a 8.1.0 issue?

Thank you

Following Symphony tutorial on Forms, it seems a good practice to use entities to manage forms data and validation https://symfony.com/doc/current/forms.html#validating-forms
How would one use Symphony Entity in demosymphonyform example ?

I have tried to create a modern module in Prestashop 1.7.7.3, it has a custom grid which displays correctly, all the data are there but the javascript based functions are not working.
The next thing I did was including the necessary js files like in the example module called demodoctirne but when I tried to use the npm run build (or dev) commands I have run into an error message:

ERROR in /var/www/html/admin-dev/themes/new-theme/js/components/grid/extension/bulk-action-checkbox-extension.js
Module build failed: Error: Couldn't find preset "env" relative to directory

Of course I used npm install, a bundle file was created and it is included in the template file, in the browser console I get a similar error message when the page with the grid loads:

Uncaught Error: Module build failed: Error: Couldn't find preset "env" relative to directory

I customized the common.js and the index.js which looks like this:

var $ = window.$;
import Grid from '@components/grid/grid';
import ReloadListActionExtension from '@components/grid/extension/reload-list-extension';
import ExportToSqlManagerExtension from '@components/grid/extension/export-to-sql-manager-extension';
import FiltersResetExtension from '@components/grid/extension/filters-reset-extension';
import SortingExtension from '@components/grid/extension/sorting-extension';
import LinkRowActionExtension from '@components/grid/extension/link-row-action-extension';
import SubmitGridExtension from '@components/grid/extension/submit-grid-action-extension';
import SubmitBulkExtension from '@components/grid/extension/submit-bulk-action-extension';
import BulkActionCheckboxExtension from '@components/grid/extension/bulk-action-checkbox-extension';
import SubmitRowActionExtension from '@components/grid/extension/action/row/submit-row-action-extension';


$(() => {
  const customGrid = new Grid('customGrid');

  customGrid.addExtension(new ReloadListActionExtension());
  customGrid.addExtension(new ExportToSqlManagerExtension());
  customGrid.addExtension(new FiltersResetExtension());
  customGrid.addExtension(new SortingExtension());
  customGrid.addExtension(new LinkRowActionExtension());
  customGrid.addExtension(new SubmitGridExtension());
  customGrid.addExtension(new SubmitBulkExtension());
  customGrid.addExtension(new BulkActionCheckboxExtension());
  customGrid.addExtension(new SubmitRowActionExtension());
});

This is the part in the common.js i changed:

module.exports = {
  externals: {
    jquery: 'jQuery',
  },
  entry: {
    customGrid: './customGrid',
  },
  output: {
    path: path.resolve(__dirname, '../../views/js'),
    filename: '[name].bundle.js',
    libraryTarget: 'window',
    library: '[name]',
  },
  resolve: {
    extensions: ['.js', '.vue', '.json'],
    alias: {
      '@components': psComponentsDir,
    },
  },
  module: {
    rules: [
      {
        test: /\.js$/,
        include: path.resolve(__dirname, '../customGrid'),
        use: [{
          loader: 'babel-loader',
          options: {
            presets: [
              ['es2015', {modules: false}],
            ],
          },
        }],
      },
      {
        test: /\.js$/,
        include: psJsDir,
        use: [{
          loader: 'babel-loader',
          options: {
            presets: [
              ['es2015', {modules: false}],
            ],
          },
        }],
      },

Hi guys, @matks ,

Hope you are all well !

I am working on manticoresearch module for prestashop and I would like to override how the getlist function generate tables in the admin panel for orders, customers, products.

Since I am using the version 1.7.7.0, and legacy overrides are not working, what is the process now for overriding these classes in a non intrusive way ?

Ps. I have read the documentation but still confused on how to do that.

Any example would be just awesome. :-)

Cheers,
Luc Michalski

Describe the bug

Demo doctrine module crashes when 2 languages are enabled in BO and a new quote is created but one language field is not filled in.

Expected behavior

Demo doctrine module should not crash when 2 languages are enabled in BO and a new quote is created but one language field is not filled in.

It should either warn user that both language fields must be filled in, or support an empty field for one language.

Steps to Reproduce

Steps to reproduce the behavior:

1. Install demodoctrine module v1.0.0
2. Make sure your shop has 2 languages enabled in BO
3. Click on 'configure' to go on administration page of demodoctrine module
4. Click 'Add a new quote'
5. Fill in "author name"
6. Fill in "Content" for one language, leave the other language empty for "Content"
7. Submit, see Type Error

Screenshots

Additional information

• PrestaShop version: 1.7.8.x
• PHP version: 7.4

SqlFilters MIN_MAX is missing in the demo_grid example...

Related PRs:

#122
PrestaShop/PrestaShop#31987

We should plug-in Travis to run what tests we have 😄 demonstrating how to plug a module to CI

When the module demoextendtemplates is installed, this fatal error appears:

How to reproduce?

• Install the module
• Try to create a backoffice order

Multiple items should be homogenized in example modules to make it easier for developers to navigate them.

• Module naming
• Namespace naming
• README
• Composer configuration (remember it needs "prepend-autoloader": false)
• Logo
• Folder structure
• License headers

Hi @matks ,

Hope you are all well !

I was looking for an example module for extending the product form in prestashop and just said to myself that it would have been awesome to have a small screenshot per example in each READMEs ^^

Thanks for any insights or inputs on this thought.

Cheers,
Luc Michalski

I've only tested this on 2 of the demo modules so far, demo_grid and demodoctrine.
When you try to compile the webpack assets for the modules, they all seem to fail.

Could the modules be updated so that they correctly compile under Prestashop 8? And providing step by step details on how to do so would also be very helpful for others

https://devdocs.prestashop-project.org/8/development/components/global-components/

For the moment the modules do not work on prestashop 8. Most often when accessing the configuration route of the module, for example :

• demo_grid
• democonsolecommand
• democontrollertabs
• demodoctrine
• demoextendgrid
• demoextendsymfonyform1
• demoextendsymfonyform2
• demoextendsymfonyform3
• demojsrouting
• demomultistoreform
• demooverrideobjectmodel
• demoproductform
• demosymfonyform
• demovieworderhooks
• #154

The module can be installed and does not throw any errors but does not add any new fields to the product form. I am trying to learn module development and this just puzzled me especially when the version inside the module is set to min 8.0.0.

It seems like the hookActionProductFormBuilderModifier is no longer being called. I tried to throw an error on the first line of that function and it does not break anything in the product form when it's loaded.

There is confusion about Demo Symfony Form module 1 because the module demonstrates 2 things:

• how to use a CQRS in a module
• how to use hooks to add new field to a Symfony form

Some community developers think that the two must be together although actually you can choose to use CQRS or not to add new field to a Symfony form.

In order to clear the confusion I will

• Modify demoextendsymfonyform1 to drop the use of CQRS - see #35
• Copy demoextendsymfonyform1 as demoextendsymfonyform3 where CQRS will be used - #33

Hi

The demo modules have been extremely useful in adapting modules to use modern controllers and Ux.

I wonder if I could request a new demo module which demonstrates how to implement tabs in the configuration of a module using new Symfony controllers and twig templates.

The attached screnshot shows the kind of tabs I am referring to.

Multistore module v1.1 scope

• On blocks listing, add a list of assigned shops in the All shops context (as available on Link list module)
• Do not use Bootstrap Colorpicker from CDN, use PrestaShop Colorpicker component
• Enable compatibility with > 1.7.8.0

public function hookActionPerformancePageForm(&$params)
    {
        /* @var $formBuilder \Symfony\Component\Form\FormBuilder */
        $formBuilder = $params['form_builder'];

        $cacheForm = $formBuilder->get('caching');
        $cachingSystemForm = $cacheForm->get('caching_system');

        $options = $cachingSystemForm->getOption('choices');
        $options['redis'] = 'redis';
        $cachingSystemForm->add('4', \Symfony\Component\Form\Extension\Core\Type\RadioType::class, [
            'value' => 'CacheRedis',
            'label' => $this->getLabel(),
            'disabled' => $this->getDisabled()
        ]);
//        dump($cachingSystemForm);
//        die();

    }

i can see the redis options.but after saved,the parameters.php 'ps_caching' not change

Hi
I have instaled DemoExtendGrid module at PrestaShop 1.7.7.4
but it does not work at all!

We need more examples:

• how to point original route to a different controller
• how to override a service
• maybe some other valid examples of how to work with service container extensibility features directly from the modules

All modules present in this repository have to be tested against PrestaShop 8.1.

• demo_grid
• democonsolecommand
• democontrollertabs
• demodoctrine
• demoextendgrid
• demoextendsymfonyform1
• demoextendsymfonyform2
• demoextendsymfonyform3
• demoextendtemplates
• demojsrouting
• demomoduleroutes
• demomultistoreform
• demooldproductpagehooks
• demooverrideobjectmodel
• demoproductform
• demosymfonyform
• demovieworderhooks
• demowsextend

Initial suggestion by @jolelievre #35 (comment)

DemoExtendSymfonyPage
DemoExtendMigratedPage
DemoExtendObjectInSymfony
DemoExtendCustomerInSymfony

As Prestashop charges forward with leveraging more of Symfony code, Prestashop developers like myself are keen to adopt this approach as much as possible and these demo modules provide a encouraging start.

In relation to the demosymfony module, it would be great if the following could be demonstrated:

• Saving to a object model (rather than configuration)
• Rendering and processing a symfony form in the displayAdminProductsExtra hook

Additionally, it seems there is significant boilerplate code required to setup forms in a module (services, classes, and even javascript code). Are there any command line utilities available which could help developers generate a simple form?

When I try to create a new quote in demodoctrine I get the following error:

Attempted to load class "LegacyLayout" from the global namespace.
Did you forget a "use" statement?

CRITICAL20:22:59 | php | Class 'LegacyLayout' not found
CRITICAL20:22:59 | request | Uncaught PHP Exception Symfony\Component\Debug\Exception\ClassNotFoundException: "Attempted to load class "LegacyLayout" from the global namespace. Did you forget a "use" statement?" at /var/www/prestashop/classes/controller/AdminController.php line 3674

Thanks a lot.

Finish the DemoExtendGrid module by implementing the button behavior

See @todo at https://github.com/PrestaShop/example-modules/blob/master/demoextendgrid/demoextendgrid.php#L78

We started usage of phpstan into Demo View Order Hooks module however it is not complete.

• make it complete
• make it run by Travis
• write about it into the README to promote/demonstrate phpstan usage

• demo-cqrs-hooks-usage-module: demo example for hooks / v1.7.6 => WIP #17
• doctrine: dmo example for Doctrine usage / v? => ?
• customers: demo example for grid hooks / v1.7.5 or v1.7.4 => ?
• crea_clearcache: demo example to add a button in layout/ v? => ?

In this documentation page, it is written that TranslateType should be used instead of TranslatableType with a FormattedTextareaType field.

If you wish to use FormattedTextareaType as type, your base type must be TranslateType instead of TranslatableType. Do not forget to add the option hideTabs at true if you want to display the languages list above the WYSIWYG.