Jump to content

Future of Padloper - New Project Lead Announcement


Recommended Posts

  • 1 month later...
  • 2 weeks later...
  • 3 weeks later...
  • 3 weeks later...
  • 1 month later...
  • 2 months later...
On 6/23/2020 at 8:59 PM, desbest said:

Padloper 2 will not support the current ‘any page can be a product’ paradigm. Technically, products will still be pages. However, all products will utilise the same Padloper template. These will be in


What does this mean? What's the reason for the change?

On 6/24/2020 at 8:33 AM, diogo said:

@desbest The answers to your questions are on that very same post:


Padloper 2 will be a major release that incorporates a new, central backend shop for Padloper. This will be a new process module that pulls from the existing parts of Padloper (data models, etc) into one interface (more on this below). This version will also be extensible in the frontend, allowing for the plugging in of a new, optional, commercial frontend shop (full featured shop profile).



A new backend interface will be the major visual difference between the existing Padloper and Padloper 2. It goes beyond visual differences though. The new backend will be the single gateway for managing all shop-related features, both current and new ones.



Sorry but I'm not quite sure what this means.

Can someone explain the difference of the old system of every page can be a product, and the new system of it not being that way and only pages with the padloper template can be a product?

But people can decide what fields belong to each template, and with different types of products, it doesn't make sense to have the same template (ie. padloper) for each product.

What are the advantages and disadvantages of the two?

Can someone explain the difference of this further to me?

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...