Jump to content
Gadgetto

SnipWire - Snipcart integration for ProcessWire

Recommended Posts

Thanks for your attention on those hookable methods, Gadgetto. Those will definitely be necessary for launching this site (the subscription pause button will get us in a lot of trouble otherwise!)

Another item for the list: when a user role with snipwire-dashboard permissions clicks on the additional tabs (Orders, Subscriptions, Abandoned Carts, Customers, Products, Discounts) within the Dashboard, they reach the 404 page instead. 

Share this post


Link to post
Share on other sites

I have another issue to report.

When I:

  • use "+ Add New" buttons to add a new page with my product template (as children of any of the three allowed parent templates)
  • enter the page Title on the admin /page/add/
  • hit Save

I get the error "New page '/page/path/' must be saved before files can be accessed from it"

If I uninstall SnipWire, the error message goes away. The product templates are my own, not the default SnipWire templates.

Share this post


Link to post
Share on other sites
5 hours ago, creativejay said:

I have another issue to report.

When I:

  • use "+ Add New" buttons to add a new page with my product template (as children of any of the three allowed parent templates)
  • enter the page Title on the admin /page/add/
  • hit Save

I get the error "New page '/page/path/' must be saved before files can be accessed from it"

If I uninstall SnipWire, the error message goes away. The product templates are my own, not the default SnipWire templates.

Do you have a hook on path method of PagefilesManager class?

I’ll try to reproduce this behavior, but I’d need more infos. Could you please send me the complete stack trace of the exception? You can use TracyDebugger for this.

How does your product template look like?

Share this post


Link to post
Share on other sites
On 3/10/2020 at 7:15 PM, creativejay said:

Thanks for your attention on those hookable methods, Gadgetto. Those will definitely be necessary for launching this site (the subscription pause button will get us in a lot of trouble otherwise!)

I just read you’d like to use subscriptions feature? Subscriptions are not yet supported by SnipWire.

Share this post


Link to post
Share on other sites
On 3/10/2020 at 7:15 PM, creativejay said:

Another item for the list: when a user role with snipwire-dashboard permissions clicks on the additional tabs (Orders, Subscriptions, Abandoned Carts, Customers, Products, Discounts) within the Dashboard, they reach the 404 page instead. 

I’ll have a look at this!

BTW, could you please file your issues on SnipWires GitHub repo? it is hard to keep the overview here in the forum.

Share this post


Link to post
Share on other sites

UPDATE 2020-03-21

SnipWire 0.8.5 (beta) released!

This update improves SnipWires webhooks interface and provides some other fixes and additions:

  • Catch module settings access for non super users
  • Fixes [#2] Dashboard not accessible for non SuperUsers
  • Added documentation (php comments) to Webhooks class and hookable event handler methods
  • All Webhooks event handler methods now have a return value (Snipcart payload)

Hookable event handler methods:

All hookable event handler methods will return an array containing payload Snipcart sent to your endpoint.
In addition the following class properties will be set:

$this->payload (The payload Snipcart sent to your endpoint)
$this->responseStatus (The response status your endpoint sent to Snipcart)
$this->responseBody (The response body your endpoint sent to Snipcart)

(Use the appropriate getter methods to receive these values!)

How to use the hookable event handler methods (sample):

$webhooks->addHookAfter('handleOrderCompleted', function($event) {
    $payload = $event->return';
    //... your code here ...
}); 

PLEASE NOTE: those hooks will currently only work when placed in init.php or init() or ready() module methods!
 

  • Like 1

Share this post


Link to post
Share on other sites
On 3/11/2020 at 5:34 PM, creativejay said:

I have another issue to report.

When I:

  • use "+ Add New" buttons to add a new page with my product template (as children of any of the three allowed parent templates)
  • enter the page Title on the admin /page/add/
  • hit Save

I get the error "New page '/page/path/' must be saved before files can be accessed from it"

If I uninstall SnipWire, the error message goes away. The product templates are my own, not the default SnipWire templates.

Hi @creativejay,

do you still have this issue?

If so, could you please file an issue in SnipWires GitHub repo and provide more information: https://github.com/gadgetto/SnipWire/issues

I could not reproduce this problem but I think I have too little information.

Share this post


Link to post
Share on other sites

Hi there, thanks so much for working as hard as you have been/still are on this module! I'm testing it out at the moment, and have come up against the error that was previously reported:

Quote

Can’t save page 0: /custom-cart-fields/: It has no parent assigned

Having dug into the code, I think I found the cause. My test PW installation is in a subdirectory - not its own host - and snipWireRootUrl returns the full path include the folders:

/misc/pw-snipwire/processwire/setup/snipwire/

In the installer, as this variable is only used to set the parent page for custom-cart-fields, could ExtendedInstaller.php be updated to use the path instead of full URL?

I updated it like this, re-installed, and it worked:

// In ExtendedInstaller::__construct():

$this->snipWireRootPath = rtrim($this->wire('pages')->findOne('template=admin, name=snipwire')->path, '/') . '/';

// in _installPage():

// Page "parent" key may have "string tags"
$parent = \ProcessWire\wirePopulateStringTags(
    $item['parent'],
    array('snipWireRootPath' => $this->snipWireRootPath)
);

// In SystemResources.php

'parent' => '{snipWireRootPath}',

 

  • Like 2

Share this post


Link to post
Share on other sites
1 hour ago, Craig said:

Hi there, thanks so much for working as hard as you have been/still are on this module! I'm testing it out at the moment, and have come up against the error that was previously reported:

Having dug into the code, I think I found the cause. My test PW installation is in a subdirectory - not its own host - and snipWireRootUrl returns the full path include the folders:

/misc/pw-snipwire/processwire/setup/snipwire/

In the installer, as this variable is only used to set the parent page for custom-cart-fields, could ExtendedInstaller.php be updated to use the path instead of full URL?

I updated it like this, re-installed, and it worked:


// In ExtendedInstaller::__construct():

$this->snipWireRootPath = rtrim($this->wire('pages')->findOne('template=admin, name=snipwire')->path, '/') . '/';

// in _installPage():

// Page "parent" key may have "string tags"
$parent = \ProcessWire\wirePopulateStringTags(
    $item['parent'],
    array('snipWireRootPath' => $this->snipWireRootPath)
);

// In SystemResources.php

'parent' => '{snipWireRootPath}',

 

Oh, you are right for sure! Thanks, I'll fix this.

Share this post


Link to post
Share on other sites

Thanks! 🙂

Share this post


Link to post
Share on other sites
On 3/21/2020 at 1:04 PM, Gadgetto said:

Hi @creativejay,

do you still have this issue?

If so, could you please file an issue in SnipWires GitHub repo and provide more information: https://github.com/gadgetto/SnipWire/issues

I could not reproduce this problem but I think I have too little information.

I wasn't able to correct it, but the website had to launch so I uninstalled the Module and am using the direct API for Snipcart in the php templates and their dashboard for managing orders.

Before I uninstalled, I couldn't find a single logged error anywhere.

Share this post


Link to post
Share on other sites

UPDATE 2020-04-06

SnipWire 0.8.6 (beta) released!

This update adds support for Snipcart subscriptions and also fixes some problems:

  • Finished subscriptions dashboard section
  • Added support for Snipcart subscriptions
  • Added necessary fields for subscription products
  • Added debug output for webhooks request payload data
  • Updated MarkupSnipWire to output subscription data-item-* tags
  • Fixed deletion of segmented caches
  • Fixed display of empty image field in product details
  • Fixed a problem with namespace in Countries.php
  • Fixed a problem with duplicate SKU check on page save
  • Fixed [#3] Installer error: Can’t save page 0: /custom-cart-fields/: It has no parent assigned

Please note:

The additional fields required for providing subscription based products are automatically installed with this update! You need to create a new template (best is to use the snipcart-product template as a base) and add these fields manually.

Snipcart subscriptions are only supported when using the Stripe payment gateway!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   1 member

  • Similar Content

    • By bernhard
      #######################
      Please use the new RockFinder2
      #######################
      WHY?
      This module was built to fill the gap between simple $pages->find() operations and complex SQL queries.
      The problem with $pages->find() is that it loads all pages into memory and that can be a problem when querying multiple thousands of pages. Even $pages->findMany() loads all pages into memory and therefore is a lot slower than regular SQL.
      The problem with SQL on the other hand is, that the queries are quite complex to build. All fields are separate tables, some repeatable fields use multiple rows for their content that belong to only one single page, you always need to check for the page status (which is not necessary on regular find() operations and therefore nobody is used to that).
      In short: It is far too much work to efficiently and easily get an array of data based on PW pages and fields and I need that a lot for my RockGrid module to build all kinds of tabular data.

      Basic Usage

       
      Docs & Download
      https://modules.processwire.com/modules/rock-finder/
      https://github.com/BernhardBaumrock/RockFinder
       
      Changelog
      180817, v1.0.6, support for joining multiple finders 180810, v1.0.5, basic support for options fields 180528, v1.0.4, add custom select statement option 180516, change sql query method, bump version to 1.0.0 180515, multilang bugfix 180513, beta release <180513, preview/discussion took place here: https://processwire.com/talk/topic/18983-rocksqlfinder-highly-efficient-and-flexible-sql-finder-module/
    • By MoritzLost
      TrelloWire
      This is a module that allows you to automatically create Trello cards for ProcessWire pages and update them when the pages are updated. This allows you to setup connected workflows. Card properties and change handling behaviour can be customized through the extensive module configuration. Every action the module performs is hookable, so you can modify when and how cards are created as much as you need to. The module also contains an API-component that makes it easy to make requests to the Trello API and build your own connected ProcessWire-Trello workflows.
      Features
      All the things the module can do for you without any custom code: Create a new card on Trello whenever a page is added or published (you can select applicable templates). Configure the target board, target list, name and description for new cards. Add default labels and checklists to the card. Update the card whenever the page is updated (optional). When the status of the card changes (published / unpublished, hidden / unhidden, trashed / restored or deleted), move the card to a different list or archive or delete it (configurable). You can extend this through hooks in many ways: Modifiy when and how cards are created. Modify the card properties (Target board & list, title, description, et c.) before they are sent to Trello. Create your own workflows by utilizing an API helper class with many convenient utility methods to access the Trello API directly. Feedback & Future Plans
      Let me know what you think! In particular:
      If you find any bugs report them here or on Github, I'll try to fix them. This module was born out of a use-case for a client project where we manage new form submissions through Trello. I'm not sure how many use-cases there are for this module. If you do use it, tell me about it! The Trello API is pretty extensive, I'll try to add some more helper methods to the TrelloWireApi class (let me know if you need anything in particular). I'll think about how the module can support different workflows that include Twig – talk to me if you have a use-case! Next steps could be a dashboard to manage pages that are connected to a Trello card, or a new section in the settings tab to manage the Trello connection. But it depends on whether there is any interest in this 🙂 Links
      Repository on Github Complete module documentation (getting started, configuration & API documentation) [Module directory pending approval] Module configuration

    • By MoritzLost
      Process Cache Control
      This module provides a simple solution to clearing all your cache layers at once, and an extensible interface to perform various cache-related actions.
      The simple motivation behind this module was that I was tired of manually clearing caches in several places after deploying a change on a live site. The basic purpose of this module is a simple Clear all caches link in the Setup menu which clears out all caches, no matter where they hide. You can customize what exactly the module does through it's configuration menu:
      Expire or delete all cache entries in the database, or selectively clear caches by namespace ($cache API) Clear the the template render cache. Clear out specific folders inside your site's cache directory (/site/assets/cache) Clear the ProCache page render cache (if your site is using ProCache) Refresh version strings for static assets to bust client-side browser caches (this requires some setup, see the full documentation for details). This is the basic function of the module. However, you can also add different cache management action through the API and execute them through the module's interface. For this advanced usage, the module provides:
      An interface to see all available cache actions and execute them. A system log and logging output on the module page to see verify what the module is doing. A CacheControlTools class with utility functions to clear out different caches. An API to add cache actions, execute them programmatically and even modify the default action. Permission management, allowing you granular control over which user roles can execute which actions. The complete documentation can be found in the module's README.
      Plans for improvements
      If there is some interest in this, I plan to expand this to a more general cache management solution. I particular, I would like to add additional cache actions. Some ideas that came to mind:
      Warming up the template render cache for publicly accessible pages. Removing all active user sessions. Let me know if you have more suggestions!
      Links
      https://github.com/MoritzLost/ProcessCacheControl ProcessCacheControl in the Module directory CHANGELOG in the repository Screenshots


    • By Macrura
      PrevNextTabs Module
      Github: https://github.com/outflux3/PrevNextTabs
      Processwire helper modules for adding page navigation within the editor.
      Overview
      This is a very simple module that adds Previous and Next links inline with the tabs on the page editor. Hovering over the tab shows the title of the previous or next page (using the admin's built in jqueryUI tooltips.)
      Usage
      This module is typically used during development where you or your editors need to traverse through pages for the purpose of proofing, flagging and/or commenting. Rather than returning to the page tree or lister, they can navigate with these links.
      Warnings
      If you are using PW version 2.6.1 or later, the system will prevent you from leaving the page if you have unsaved edits.
      For earlier versions, to avoid accidentally losing changes made to a page that might occur if a user accidentally clicks on one of these, make sure to have the Form Save Reminder module installed.
      http://modules.processwire.com/modules/prev-next-tabs/
×
×
  • Create New...