Padloper (ProcessWire Modul) - Versionsgeschichte

37.49.72.8: /* Kurzanleitung */

2020-11-16T18:09:38Z

Kurzanleitung

Steff am 23. April 2020 um 09:21 Uhr

2020-04-23T09:21:00Z

Steff am 23. April 2020 um 09:20 Uhr

2020-04-23T09:20:05Z

37.49.72.8 am 23. April 2020 um 06:11 Uhr

2020-04-23T06:11:13Z

37.49.72.8 am 22. April 2020 um 21:56 Uhr

2020-04-22T21:56:29Z

37.49.72.8 am 22. April 2020 um 21:30 Uhr

2020-04-22T21:30:48Z

37.49.72.8 am 22. April 2020 um 21:29 Uhr

2020-04-22T21:29:41Z

37.49.72.8 am 22. April 2020 um 21:28 Uhr

2020-04-22T21:28:26Z

37.49.72.8: /* Installation */

2020-04-22T21:27:11Z

Installation

149.172.225.28 am 16. März 2018 um 11:23 Uhr

2018-03-16T11:23:28Z

@@ Zeile 14: / Zeile 14: @@
 == Kurzanleitung ==
 === Installation ===
-* Upload PaymentModule into ''/site/modules/PaymentModule'' and install it through ProcessWire admin (Achtung es gibt eine PW2 und eine PW3 Version)
+* PaymentModule ''/site/modules/PaymentModule'' installieren (Achtung es gibt eine PW2 und eine PW3 Version)
 ** https://github.com/apeisa/PaymentModule/tree/PW3
-* Upload PaymentInvoice into ''/site/modules/PaymentInvoice'' and install it through ProcessWire admin (Achtung es gibt eine PW2 und eine PW3 Version)
+* PaymentInvoice into ''/site/modules/PaymentInvoice'' installieren (Achtung es gibt eine PW2 und eine PW3 Version)
 ** https://github.com/apeisa/PaymentInvoice/tree/PW3
-* Install core module "'''ProFields: Page Table'''" if not already installed
+* Core module "'''ProFields: Page Table'''" installieren
 * Upload Padloper into ''/site/modules/Padloper/'' and install PadLoper modules through ProcessWire admin (please note that there is separate distro for PW 3.0)
 Auf die Rechte achten wenn was nicht gefunden wird. Im Payment Module kann bei Choose active payment modules noch nichts ausgewählt werden solange nicht die erforderlichen anderen Module installiert sind. Kann man aber auch im Nachgang machen. Eventuell in anderer Reichenfolge installieren ( Todo -> Test)

@@ Zeile 1: / Zeile 1: @@
 Padloper ist ein ProcessWire Pro Modul ( kostenpflichtig ) für die Umsetzung von eCommerce.
-Padloper 1 wurde von Apeisa entwickelt und ging jetzt an Kogondo über - Padloper 2 wird nicht kompatibel sein und soll im laufe 2020 fertig werden.
+Padloper 1 wurde von Apeisa entwickelt und ging jetzt an Kogondo über - Padloper 2 wird '''nicht''' kompatibel sein und soll im Laufe 2020 fertig werden. Auch das Konzept jedes Produkt ist eine Seite wird nicht genauso gehandhabt.
 * [[:File:padloper3-1.zip]] Padloper Modul PW3

@@ Zeile 2: / Zeile 2: @@
 Padloper 1 wurde von Apeisa entwickelt und ging jetzt an Kogondo über - Padloper 2 wird nicht kompatibel sein und soll im laufe 2020 fertig werden.
-* [[:File:PaymentInvoice-master.zip]] Invoice Modul
+* [[:File:padloper3-1.zip]] Padloper Modul PW3
-* [[:File:PaymentModule-master.zip]] Payment Modul
+* [[:File:PaymentInvoice-PW3.zip]]
-* [[:File:padloper3-1.zip]] Padloper Modul
+* [[:File:PaymentModule-PW3.zip]]
-* [[:File:padloper-1_1_2.zip]] Padloper Modul (alte Version)
+* [[:File:PaymentInvoice-master.zip]] Invoice Modul PW2
 == Links ==
   https://www.padloper.pw/documentation/installing-padloper/

← Nächstältere Version		Version vom 23. April 2020, 06:11 Uhr
Zeile 135:		Zeile 135:
	</syntaxhighlight>		</syntaxhighlight>
	That example will do few things: if add to cart fails, it alerts the error message. There might be two reasons: form wasn't valid (probably due required modifier missing) or the product is out of stock. In case of success, it will update few html elements (#totalQty, #numberOfTitles and #totalAmount) with the updated values from your cart. Those elements you should add into your template markup.		That example will do few things: if add to cart fails, it alerts the error message. There might be two reasons: form wasn't valid (probably due required modifier missing) or the product is out of stock. In case of success, it will update few html elements (#totalQty, #numberOfTitles and #totalAmount) with the updated values from your cart. Those elements you should add into your template markup.
		+
		+	== Digital Downloads ==
		+	https://www.padloper.pw/documentation/digital-downloads/
		+
		+	PadLoper supports selling digital downloads
		+	By installing ProcessPadDownloads module you get new admin section under setup called PadLoper Downloads (you did know that it is possible to rename and -arrange these pages?). This section is super simple, it allows you to add, edit and remove digital downloads and define few rules for their accessibility.
		+
		+	In PadLoper it is separate process to attach these files into products. While two step process is somewhat clumsy when editing the products, it allows you to use same file in more than one product.
		+
		+	For attaching downloadable files into a project we need a downloads-field. So go ahead and install FieldtypeDownloads and create one field using that fieldtype. After attaching the new field into your product template, you can go edit your products and add one or more downloads per files. Currently it's using AsmSelect as an inputfield, but I am looking for supporting at least AutoComplete also, in case there are thousands of downloadables.
		+
		+	=== Securing the download files ===
		+	ProcessPadDownloads saves the files inside '''/site/assets//'''. They are accessible by default, if you haven't set ProcessWire to secure the files. This can be done from /site/config.php by adding (or uncommenting) the line:
		+
		+	$config->pagefileSecure = true;
		+	Then only roles which have access into admin can access the files directly. The actual url directly to a file is never visible to customer, so it won't be total disaster if pagefileSecure is not set true.
		+
		+	=== Delivery of the files ===
		+	It's up to shipping module to offer the download links to customer, after succesful payment. Downloads are done using '''download codes''', which have certain rules like "valid until" -date and max. download count. Download links have formation of www.yourshop.com/d/?code=23456789
		+
		+	If the download code is wrong or not valid anymore, then 404 page is send instead of file download. Currently ShippingEmail supports downloadable products.

@@ Zeile 9: / Zeile 9: @@
   https://www.padloper.pw/documentation/installing-padloper/
   https://padloper.pw/documentation/making-it-ajax/ (Ajax Warenkorb)
 == Kurzanleitung ==
 === Installation ===

← Nächstältere Version		Version vom 22. April 2020, 21:30 Uhr
Zeile 91:		Zeile 91:
	=== Paypal ===		=== Paypal ===
	[[Padloper und PayPal Express (ProcessWire)]]		[[Padloper und PayPal Express (ProcessWire)]]
		+
		+	== AJAX Warenkorb ==
		+	Making it AJAX
		+	It's very easy to make add to cart work ajaxified. Here is simple tutorial to show you how.
		+
		+	As you probably already know, adding "add to cart" button into your templates is pretty easy:
		+
		+	$modules->get("PadRender")->addToCart($product, $askQty = true);
		+	This adds pretty verbose markup for the button (it uses ProcessWire's inputfields, looking for a way to make it shorter), but that is "full featured" - meaning if you add modifiers there, it will also validate those nicely. By default add to cart process is simple:
		+
		+	Customer clicks button and form submits
		+	Form is validated (modifiers are valid, no zero or negative amount of products added etc)
		+	If not valid, form is rendered again with error messages
		+	If valid, then product is added into cart and customer is redirected back to current page with cart updated, and productId=123 as a get param (where 123 is id for the added product).
		+	To ajaxify this whole process we need to submit the form with ajax. Form can be submitted as is and Padloper will return results as JSON. Here is complete jQuery example to ajaxify the add to cart buttons:
		+
		+	<syntaxhighlight lang="javascript">
		+	// jQuery example of how to make add to cart buttons ajaxified
		+	$( ".padloper-cart-add-product" ).submit(function( event ) {
		+
		+	event.preventDefault();
		+	var $form = $(this);
		+	var url = $form.attr("action");
		+
		+	// Send the data using post
		+	var posting = $.post(url, $form.serialize());
		+
		+	posting.done(function(data) {
		+	if (data.errors) {
		+	var str = '';
		+	$.each(data.errors, function(i, val) {
		+	str = str + val;
		+	});
		+	alert(str);
		+	} else {
		+	$("#totalQty").html(data.totalQty);
		+	$("#numberOfTitles").html(data.numberOfTitles);
		+	$("#totalAmount").html(data.totalAmount);
		+	}
		+	});
		+	});
		+	</syntaxhighlight>
		+	That example will do few things: if add to cart fails, it alerts the error message. There might be two reasons: form wasn't valid (probably due required modifier missing) or the product is out of stock. In case of success, it will update few html elements (#totalQty, #numberOfTitles and #totalAmount) with the updated values from your cart. Those elements you should add into your template markup.

← Nächstältere Version		Version vom 22. April 2020, 21:28 Uhr
Zeile 1:		Zeile 1:
	Padloper ist ein ProcessWire Pro Modul ( kostenpflichtig ) für die Umsetzung von eCommerce.		Padloper ist ein ProcessWire Pro Modul ( kostenpflichtig ) für die Umsetzung von eCommerce.
		+	Padloper 1 wurde von Apeisa entwickelt und ging jetzt an Kogondo über - Padloper 2 wird nicht kompatibel sein und soll im laufe 2020 fertig werden.

	* [[:File:PaymentInvoice-master.zip]] Invoice Modul		* [[:File:PaymentInvoice-master.zip]] Invoice Modul

← Nächstältere Version		Version vom 16. März 2018, 11:23 Uhr
Zeile 81:		Zeile 81:
	== Lokalisierung ==		== Lokalisierung ==
	Über das Language Modul kann automatisch ein Index angelegt werden. Wenn man alles übersetzt hat, kann man die Übersetzung exportieren.		Über das Language Modul kann automatisch ein Index angelegt werden. Wenn man alles übersetzt hat, kann man die Übersetzung exportieren.
		+
		+	== Zahlungsmethoden ==
		+	=== Paypal ===
		+	[[Padloper und PayPal Express (ProcessWire)]]