Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Gadgetto last won the day on January 14

Gadgetto had the most liked content!

Community Reputation

282 Excellent

About Gadgetto

  • Rank
    Sr. Member
  • Birthday 10/05/1966

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Mattersburg / Austria

Recent Profile Visitors

798 profile views
  1. I have pushed a small fix regarding the new "multiple product templates" feature. Please redownload at GitHub.
  2. I just implemented your feature request! 🙂 Multiple product-templates are now allowed! Just get latest version on GitHub!
  3. The problem is, taxes handling needs to be bomb proof, otherwise the store merchant could get problems with the taxes authorities. Taxes is one of the last things which needs to be finished before the first release. I'm in contact with the Snipcart guys and I think this should be solved in short time.
  4. UPDATE 2020-01-14 What's new - what has been added - what has changed: I had to completely remove the DateRangePicker.js library because of quirks on mobile devices and accessibility problems. The dashboard date range picker has been completely rebuilt with default ProcessWire fields - and I think it looks great + its now fully working on mobile devices + its more accessible! The orders detail panel is now also capable of changing order statuses and adding order comments (including customer notifications, tracking number and tracking url) Finalized the discount editor: create, edit, delete, archive, unarchive Snipcart discounts A lot of internal fixes and enhancements One of the greatest features of the current version is the dashboard performance. I was able to increase the REST API execution speed by the factor of 2 - 2.5 times What's next: I'm still struggling with taxes handling. Especially the handling of shipping taxes is a complex thing and drives me crazy... Finishing the remaining detail panels Implementing Subscriptions Implementing Digital Products (probably not in the first release) Implementing a more flexible product template handling (probably not in the first release) DONE! And of course - release! Here are some fresh screens:
  5. Not in the first release. But multiple product templates are definitely planned.
  6. To also give it a visual representation you can additionally add: $f->addClass('ui-state-disabled');
  7. I know Jens, but I'd like to use same references as PW uses. An PW is not yet on ECMAScript 6.
  8. Sorry, for sure I meant SnipWire (I edited my post)! I don't see a reason why this shouldn't work. It probably would be the best, if you install and use the latest versions of SnipWire module and only use custom code where SnipWire isn't ready yet or is missing features you'd like to use. As I don't have a documentation available yet, please don't hesitate to ask your questions here and I'll try to help. If you find any problems/bugs or if you have suggestions for improvement while using SnipWire, it would be great if you could post back here or post an issue at GitHub so I could fix it.
  9. I have a PW panel with a button element inside. When this button is clicked, the panel should close and the button action (href is triggered via JavaScript) should be executed in the main window (from where the panel was opened). In the current state, when the button is clicked, the action is processed within the panel, which is not what I want. Here is the button code: /** @var InputfieldSubmit $btn */ $btn = $modules->get('InputfieldButton'); $btn->attr('name', 'delete_discount'); $btn->href = $this->snipWireRootUrl . 'discounts/?id=' . $item['id'] . '&action=delete_discount'; $btn->aclass = 'DeleteDiscountButton'; $btn->text = $this->_('Delete discount'); $btn->icon = 'trash'; $deleteButton = $btn->render(); Here is the JS part which is triggered when button is clicked: $('.DeleteDiscountButton').on('click', function(e) { e.preventDefault(); var a_href = $(this).attr('href'); ProcessWire.confirm( discountActionStrings.confirm_delete_discount, function() { // dialogue OK click window.location.href = a_href; } ); }); Any hints on how this could be done?
  10. I'm glad you like SnipWire! 🙂 Important: SnipWire is not yet ready for production environments! Subscriptions are on my backlog and will be definitely in the first release!
  11. Thanks for you input @flydev, I did check the technique you posted, but IMHO it's not very UX friendly. It first makes the user think that he can choose an option. I solved it in an easy way by disabling the select and an additional hidden field (as posted above).
  12. The REST API of SnipCart requires this value with each POST or PUT request, but it may not be changed once submitted.
  13. Here is the complete code - now with working simulated "readonly" InputfieldSelect:
  • Create New...