scandipwa / route717

scandipwa/route717

ScandiPWA dedicated router

magento2-module 2.4.6-2.4.9 Compatible Based on composer requirements only QA: failed OSL-3.0

ScandiPWA Route717

Module is providing custom router to properly resolve HTTP codes on specific page request.

v1.1.0 update

Custom router is now checking theme type in order to support URL rewrites.
You must ensure PWA theme type is set to 4 to utilize the options.

Installer is doing this automatically for any newly generated theme.

For already generated theme please update manually: set PWA theme type to 4 in theme table.

Installation

composer require scandipwa/route717

Description

Module is providing validators for such entities:

  1. Product (/product)
  2. Category (/category)
  3. Cms pages (/page)
  4. Cart (/cart)
  5. Root (/)

How it works

Each frontend path (Magento 2 front name) should be added to validator list in src/etc/di.xml. Depending on entity
type it might have more or less complex validation logic, to i.e. determine if specific product exists or not.
Router is only responding 200 OK to entities, which it was able to validate. Otherwise it is falling back to default
Magento 2 routers.

Customization

To add new path you must provide your own validator, that must implement ScandiPWA\Router\ValidatorInterface and
register it as an array element passed to ScandiPWA\Router\ValidationManager using di.xml.

Accessing Magento 2 default routes

In order to allow Magento 2 to handle some routes in default manner (only serverside functionality) you must allow
specific routes to be accessed by adding RegExp to src/app/etc/di.xml::ignoredURLs arguments list.

So far there are 3 paths whitelisted out of the box:

  • /newsletter/subscriber/confirm - subscribe to newsletter
  • /newsletter/subscriber/unsubscribe - unsubscribe to newsletter
  • /customer/account/confirm/ - confirm e-mail (redirect to homepage in any case, modify according to your needs)

No changelog yet

The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.

Versions
Version Stability QA Status Released
2.1.6 stable Fail 2024-04-04 09:14:47
2.1.5 stable Not tested 2023-04-10 23:33:56
2.1.4 stable Not tested 2023-02-20 15:58:10
2.1.3 stable Not tested 2023-02-14 16:54:00
2.1.2 stable Not tested 2023-02-10 13:39:05
2.1.1 stable Not tested 2023-01-11 11:25:33
2.1.0 stable Not tested 2023-01-10 12:39:57
2.0.2 stable Not tested 2021-12-09 21:15:32
2.0.1 stable Not tested 2021-09-28 19:43:47
2.0.0 stable Not tested 2020-11-19 14:00:34
1.8.0 stable Not tested 2020-09-07 10:32:08
1.7.0 stable Not tested 2020-08-25 09:29:22
1.6.2 stable Not tested 2020-06-15 13:31:27
1.6.1 stable Not tested 2020-04-08 08:09:00
1.6.0 stable Not tested 2020-04-03 14:32:36
1.5.0 stable Not tested 2020-01-21 15:13:56
1.4.2 stable Not tested 2019-10-19 17:14:15
1.4.1 stable Not tested 2019-10-19 17:00:57
1.4.0 stable Not tested 2019-10-19 16:25:30
1.3.0 stable Not tested 2019-09-12 08:29:38
1.2.0 stable Not tested 2019-07-29 11:42:16
1.1.2 stable Not tested 2019-07-23 11:52:07
1.1.1 stable Not tested 2019-06-25 09:41:51
1.1.0 stable Not tested 2019-05-10 10:00:16
1.0.0 stable Not tested 2019-03-26 10:19:34

Requires 5

Package Constraint
magento/framework *
magento/module-customer *
magento/module-store *
magento/module-url-rewrite *
magento/module-wishlist *
QA results
Tool Status Findings Summary
PHPCS Pass 0
PHPStan Fail 73 73 errors (level 4, ruleset: phpstan + bitexpert/phpstan-magento)
Cpd Pass 0
Security Pass 0
License
OSL-3.0
Make it pay

Turn an existing module into recurring revenue.

If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.