Hackasacka

Hi Bernard, Are you adding Paypal & Stripe as payment gateways as modules like RockMollie in the near future yourself? Thanks

Hi Bernhard, Thanks for the clarification regarding the payment gateway being server side and therefor more secure. It looks very good & it's great to see a live website. Thanks

Hi Bernhard, Yes, I was aware of Mollie has a Paypal option, but as our customers typically already have a Paypal account or are familiar with Paypal as a provider and therfore it is preferable to Mollie. It is very likely to be a similar process, although as you mention Alpine JS your version may be client side as opposed to server side payments? Hopefully, you'll be able to add this option in the future so RockCommerce can be an a viable solution. If you've got a developer version to look at perhaps I can add this on your behalf? Also, are there any existing websites currently using RockCommerce to have a look at? Thanks

Hi Bernhard, Is it a relatively straight forward task to implement an additional Paypal gateway with their server side v2 API oAuth based authorisation. ! have a basic version of this as a working module. I would prefer not to use Mollie and prefer Paypal as a provider due to it's popularity and fees. Can you provide a simple guide as without purchasing RockCommerce and with limited documentation of alternative payment gateways I was not sure if it would be suitable for an e-commerce project. Great that you have created a Processwire e-commerce solution! Thanks

Also, had some issues with the Processwire multi-instance sites using the latest versions and ProcessWire 3.0.123 'Compile Error: Cannot declare class FieldtypeRepeater, because the name is already in use (line 30 of...'. The error message was on the sub-domain that also had more complexity with fields and modules. Our code was bootstrapped on the sub-domain and included Processwire namespace too. As new install of the latest version worked, but actual sites with additional fields and modules did not? Further investigation and debugging highlighted that on a new install the 'Repeater' module is not installed and therefor does not cause an error? However, on the working sites renaming the folder 'FieldtypeRepeater' located in the 'wire' folder (/wire/modules/Fieldtype/FieldtypeRepeater) caused Tracy Debugger to error instead. Removing this module in addition to renaming folder ' 'FieldtypeRepeater' allowed everything to work as expected. You have to login before renaming the core module 'FieldtypeRepeater' and ignore the admin messages whilst you access the multi-instance data and create pages on the sub-domain. Not a very elegant work around, but if you only need to read and write the data temporarily at least it is possible now. Hopefully, this may help someone else work out how to fix it properly?

Also, had some issues with the Processwire multi-instance sites using the latest versions and ProcessWire 3.0.123 'Compile Error: Cannot declare class FieldtypeRepeater, because the name is already in use (line 30 of...'. The error message was on the sub-domain that also had more complexity with fields and modules. Our code was bootstrapped on the sub-domain and included Processwire namespace too. As new install of the latest version worked, but actual sites with additional fields and modules did not? Further investigation and debugging highlighted that on a new install the 'Repeater' module is not installed and therefor does not cause an error? However, on the working sites renaming the folder 'FieldtypeRepeater' located in the 'wire' folder (/wire/modules/Fieldtype/FieldtypeRepeater) caused Tracy Debugger to error instead. Removing this module in addition to renaming folder ' 'FieldtypeRepeater' allowed everything to work as expected. You have to login before renaming the core module 'FieldtypeRepeater' and ignore the admin messages whilst you access the multi-instance data and create pages on the sub-domain. Not a very elegant work around, but if you only need to read and write the data temporarily at least it is possible now. Hopefully, this may help someone else work out how to fix it properly?

Really liking the new TinyMCE editor. Does anyone know how to extend the valid elements attribute in this module so it allows any styles and also Javascript too? The Purifier is disabled in the module settings, but the source code pasted into the editor still strips out some Javascript required. There is documentation for the TinyMCE cloud version, but not sure how to do this if it is not in the module settings? https://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/form-administration/task/tinymce-allow-javascript.html Thought it may be possible in /site/modules/InputfieldTinyMCE/InputfieldTinyMCE.module.php but not sure how to do it without breaking it. tinymce.init({ extended_valid_elements : "script[language|type|src]" }); /site/modules/InputfieldTinyMCE/InputfieldTinyMCE.module.php Ryans documentation for whitelisting in the pastefilter may also allow Javascript? https://processwire.com/blog/posts/using-tinymce-6-in-processwire/#handling-user-pasted-content-with-the-em-pastefilter-em-feature It seems to be very capable, but I'm just getting used to using it as it looks so good now and would like any HTML and Javascript source code pasted in via the code window to remain in tact. Solution:- Ryan has already provided the "Custom settings JSON" under the "Input" tab of the field options for TinyMCE where you could add the new options:- { "extended_valid_elements" : "script[language|type|src],select[onclick|onchange]" } Note that the extended_valid_elements also needed to be surrounded by double quotes too. Also, there is an additional option for the form "select" element specified, so it is now possible to include <script>your Javascript here</script> and also embed it within the <select> element as an attribute too. Obviously, this is not recommended for security, but it is great to have this control over a rich text field within Processwire too.

Hi Marco, It might be simpler for you to just try the above code to see for yourself the result (just requires any valid email here not necessarily a Paypal one ):- <input type="hidden" name="business" value="YOUR_PAYPAL_EMAIL_ADDRESS"> It is possible to pay with a credit card just like "Stripe" (see bottom right of image included) too. Obviously, this would take more interaction before the transaction is completed compared with using a Paypal account directly. Paypal seem to try to obfuscate this option typically. I think it it obvious enough in this example. However, if your version has more features available now and in the future it probably makes sense to use your module instead. Regards, Hackasacka

Hi Marco, That's no problem and I look forward to trying it out now there is a version to test. Incidentally, the above code does have the option to pay with a credit card. However, you would need to process the "Instant Payment Notification" to confirm the sale at the server side if you would like to interact with the process. One advantage of this code is the ease of use and also it is unnecessary to take any details of the third party buyer as Paypal processes this themselves. Thereby, if the buyer is already logged into their Paypal account two mouse clicks results in a sale (no complicated forms to discourage continuing). It may not be ideal to have an express checkout solution if more details are needed before a sale can take place with regards to shipping and taxes, but it would be possibe to add more server side validation before posting the form too. Simple HTML Form Basics for PayPal Payments Standard https://developer.paypal.com/api/nvp-soap/paypal-payments-standard/integration-guide/formbasics/ Regards, Hackasacka

Hi Marco, It would be great to have a quick way to add "Paypal" as a payment gateway easily to Processwire and I am looking forward to trying out your new module when it is compete. In the meantime, I have been using an insecure method, but one that has not yet been abused to take a simple transaction with "Paypal". It does not handshake with Paypal, but does know the url of the site page that it is called from and appears to work quite well in practice. Although, it is not exactly comprehensive it does take you to a "Paypal" shopping cart that takes care of multiple instances of different products doing all the hard work. All you need is a "Paypal" email address a product description, a price and set the currency. Obviously, it does not remove stock or accomplish many of the more comprehensive objectives regarding taxes and shipping, but as long as you populate the fields, which could be dynamically from Processwire, you can make a sale and "Paypal" keeps all the records. The image for the "Purchase" is Bootstrap based, but you can replace this with your own image or styling. Here is the Processwire Paypal Gateway code to cut-and-paste into any page template :- <form target="paypal" action="https://www.paypal.com/cgi-bin/webscr" method="post"> <!-- Identify your business so that you can collect the payments. --> <input type="hidden" name="business" value="YOUR_PAYPAL_EMAIL_ADDRESS"> <!-- Specify a PayPal Shopping Cart Add to Cart button. --> <input type="hidden" name="cmd" value="_cart"> <input type="hidden" name="add" value="1"> <!-- Specify details about the item that buyers will purchase. --> <input type="hidden" name="item_name" value="YOUR PRODUCT DESCRIPTION - INCLUDE shipping in TOTAL"> <input type="hidden" name="amount" value="150"> <input type="hidden" name="currency_code" value="GBP"> <!-- Display the payment button. --> <input class="btn btn-primary btn--pp img-responsive" style="margin: 0 auto;" type="submit" name="submit" value="Purchase"> <img alt="" src="https://www.paypalobjects.com/en_US/i/scr/pixel.gif" width="1" height="1"> </form> This could be developed further if necessary to include more features, but maybe it is better to wait for your module? Regards, Hackasacka

Hi Kongondo, We're interested utilising Processwire for e-commerce and therefore your development of "Padloper II". We have enlisted ourselves on your Google form for beta testing. Kind regards, Nigel

Hi Greene000, Yes, having looked at your current website, we would undertake the complete transfer from Wordpress to Processwire including the design and content. Please get in touch to further discuss the migration of your website to the latest version of Processwire.

Hi Kongondo, Firstly, thank you for creating this module! We have just installed the latest version of your module "Processblog" v2.4.5 on "Processwire" version 3.0.148 and PHP v5.6 (maybe this needs updating). A couple of layout styles were tested with and without the demo templates, but the same fatal error persisted when attempting to access the "authors" tab :- "Fatal Error: Fatal Error: Call to a member function size() on boolean (line 1686 of Processblog.Module)" Here is line 1685 of Processblog.Module "$authorPhoto = !empty($author->blog_images) ?" However, with exactly the same setup, but using "Processblog" version 2.4.2 it worked perfectly. This version had a slightly different logic to achieve the same result :- " $authorPhoto = count($author->blog_images) ?" Once this was updated in your latest version it worked. Hopefully, this may help anyone who may encounter the same issue? Kind regards, Hackasacka

Hi Robin, We have now tested Processwire v3.0.123 and another Android v7.0 phone and an unknown version of Chrome with success. Also, an older Android tablet with unchecked versions of app also worked if you double-tap the "image description" input box. An alternative solution was to simply download the latest version of the Firefox v64.0.2 web browser released on the 9th of January 2019. Opera's web browser might be a useful alternative to try too? Regards, Hackasacka

Hi Robin, Just tried the oldest Processwire version I could find on GitHub of 3.0.34 released on 23 Sep 2016. This also appears to have the same problem when you try to modify "image descriptions" in that the screen keyboard does not appear. I'll see if I can try a tablet later as maybe the screen size is an issue? Regards, Hackasacka