En:Installation aid for webmasters - Versionsgeschichte

Niklas: /* Installation of the Winestro store */

2022-10-06T06:49:33Z

Installation of the Winestro store

← Nächstältere Version		Version vom 6. Oktober 2022, 08:49 Uhr
Zeile 166:		Zeile 166:

	=== Installation of the Winestro store ===		=== Installation of the Winestro store ===
	[[File:~~Winestro_installation~~.PNG \| thumb \| right \| frame \| installation links of Winestro]]		[[File:Winestro_einbau.PNG \| thumb \| right \| frame \| installation links of Winestro]]
	The Winestro store can only be built in with the iframe variant (see above) or as a stand-alone variant. The INSTALLATION LINK can be found by the winery under Order / Platt-Form-Shop on the last page. In the stand-alone variant, simply the first link / SRC of the iframe can be set. If the store is to be built in as an iframe, the customer number (yellow) must be replaced by the winery's customer number. The later page with the iframe (marked red in the picture) is also to be set in the program to solve the cookie problem (see iframe installation private store above) and to set all cookies. An automatic height change / CORS call is not possible in this variant. We recommend the installation as a stand-alone page in a new tab.		The Winestro store can only be built in with the iframe variant (see above) or as a stand-alone variant. The INSTALLATION LINK can be found by the winery under Order / Platt-Form-Shop on the last page. In the stand-alone variant, simply the first link / SRC of the iframe can be set. If the store is to be built in as an iframe, the customer number (yellow) must be replaced by the winery's customer number. The later page with the iframe (marked red in the picture) is also to be set in the program to solve the cookie problem (see iframe installation private store above) and to set all cookies. An automatic height change / CORS call is not possible in this variant. We recommend the installation as a stand-alone page in a new tab.

Niklas: /* Further installation methods / connection possibilities of stores */

2022-10-06T06:49:08Z

Further installation methods / connection possibilities of stores

← Nächstältere Version		Version vom 6. Oktober 2022, 08:49 Uhr
Zeile 141:		Zeile 141:

	== Further installation methods / connection possibilities of stores ==		== Further installation methods / connection possibilities of stores ==
	[[Datei:Generelle ~~Installationsmethoden~~.PNG \| thumb \| right \| frame \| Visualization of the interfaces (prices as of 12.08.21, the current price list applies)]]		[[Datei:Generelle einbaumethoden.PNG \| thumb \| right \| frame \| Visualization of the interfaces (prices as of 12.08.21, the current price list applies)]]
	Basically it is no problem to connect several webshops, APIs or interfaces with WBO at the same time. Also the use of an (own) store and [[Winestro]] are not mutually exclusive. Rather the opposite: WBO is designed for multi-channel sales. All possibilities of interfaces and stores you can also find in the graphic on the right.		Basically it is no problem to connect several webshops, APIs or interfaces with WBO at the same time. Also the use of an (own) store and [[Winestro]] are not mutually exclusive. Rather the opposite: WBO is designed for multi-channel sales. All possibilities of interfaces and stores you can also find in the graphic on the right.

Niklas: /* Further installation methods / connection possibilities of stores */

2022-10-06T06:48:25Z

Further installation methods / connection possibilities of stores

← Nächstältere Version		Version vom 6. Oktober 2022, 08:48 Uhr
Zeile 141:		Zeile 141:

	== Further installation methods / connection possibilities of stores ==		== Further installation methods / connection possibilities of stores ==
	[[~~File~~:~~General installation methods~~.PNG \| thumb \| right \| frame \| Visualization of the interfaces (prices as of 12.08.21, the current price list applies)]]		[[Datei:Generelle Installationsmethoden.PNG \| thumb \| right \| frame \| Visualization of the interfaces (prices as of 12.08.21, the current price list applies)]]
	Basically it is no problem to connect several webshops, APIs or interfaces with WBO at the same time. Also the use of an (own) store and [[Winestro]] are not mutually exclusive. Rather the opposite: WBO is designed for multi-channel sales. All possibilities of interfaces and stores you can also find in the graphic on the right.		Basically it is no problem to connect several webshops, APIs or interfaces with WBO at the same time. Also the use of an (own) store and [[Winestro]] are not mutually exclusive. Rather the opposite: WBO is designed for multi-channel sales. All possibilities of interfaces and stores you can also find in the graphic on the right.

Niklas: /* External control / parameter passing */

2022-10-06T06:46:41Z

External control / parameter passing

← Nächstältere Version		Version vom 6. Oktober 2022, 08:46 Uhr
Zeile 120:		Zeile 120:
	If you are technically able to do so, information can also be passed to the iframe. Just add more parameters to the installation link here and add them to the end. This allows you to build external menus or jump directly from the web page to the frame. Example:		If you are technically able to do so, information can also be passed to the iframe. Just add more parameters to the installation link here and add them to the end. This allows you to build external menus or jump directly from the web page to the frame. Example:

	[~~EINBAULINK~~]&id_grp=3 \| Calls the article group with the identifier three		[INSTALLATION LINK]&id_grp=3 \| Calls the article group with the identifier three
	[~~EINBAULINK~~]&weinnr=13 \| Calls the wine number 13.		[INSTALLATION LINK]&weinnr=13 \| Calls the wine number 13.

	Here you can pass the parameters to the iframe in several ways. An example with PHP using the framing URL would be:		Here you can pass the parameters to the iframe in several ways. An example with PHP using the framing URL would be:

	[~~EINBAULINK~~]&weinnr=<? echo $_GET["weinnr"]; ?>\| Calls the wine number 13.		[INSTALLATION LINK]&weinnr=<? echo $_GET["weinnr"]; ?>\| Calls the wine number 13.

	Another, very nicely speaking way is to include via subdomains. This is usually easy to do with most hosters. For example, you could link as follows:		Another, very nicely speaking way is to include via subdomains. This is usually easy to do with most hosters. For example, you could link as follows:

	store.weingut.de [pointing to the [~~EINBAULINK~~]]		store.weingut.de [pointing to the [INSTALLATION LINK]]
	riesling.weingut.de \| Points to [~~EINBAULINK~~]&id_grp=3 (If 3 would be the Rieslings)		riesling.weingut.de \| Points to [INSTALLATION LINK]&id_grp=3 (If 3 would be the Rieslings)
	...		...

Niklas: /* Automatic installation script (!Beta!) */

2022-10-06T06:37:25Z

Automatic installation script (!Beta!)

← Nächstältere Version		Version vom 6. Oktober 2022, 08:37 Uhr
Zeile 111:		Zeile 111:
	* user_id : can be found in the EINBAULINK		* user_id : can be found in the EINBAULINK
	* shop_id : see above,		* shop_id : see above,
	* version : The version number of your store; the current default is 15.0.		* version : The version number of your store; the current default is 16.0.

	'''Warning:''' The use of the script is currently in beta / testing stage and is at your own risk. The script must be directly at the installation point and have at least one parent node (div / body etc..) in the DOM. If the page does not load / the OnLoad events of your website are overwritten by scripts, call:		'''Warning:''' The use of the script is currently in beta / testing stage and is at your own risk. The script must be directly at the installation point and have at least one parent node (div / body etc..) in the DOM. If the page does not load / the OnLoad events of your website are overwritten by scripts, call:

Niklas: /* Compensating the cookie problem */

2022-10-06T06:33:40Z

Compensating the cookie problem

← Nächstältere Version		Version vom 6. Oktober 2022, 08:33 Uhr
Zeile 85:		Zeile 85:
	[[Datei:Umleitung.PNG \| thumb \| right \| frame \| Visualization of redirection]] The store must be called once '''standing alone'''. This allows cookies to be set and - if the customer arrives at the site via smartphone - the user has an optimal experience. After the purchase, the user is then redirected back to the website. The customer will also be redirected back if the viewport is large enough for the full view.		[[Datei:Umleitung.PNG \| thumb \| right \| frame \| Visualization of redirection]] The store must be called once '''standing alone'''. This allows cookies to be set and - if the customer arrives at the site via smartphone - the user has an optimal experience. After the purchase, the user is then redirected back to the website. The customer will also be redirected back if the viewport is large enough for the full view.

	'''So always set links to the store to the ~~EINBAUCODE~~.		'''So always set links to the store to the installation code.
	This then redirects to the built-in page if necessary.'''		This then redirects to the built-in page if necessary.'''

Niklas: /* Compensating the cookie problem */

2022-10-06T06:33:08Z

Compensating the cookie problem

← Nächstältere Version		Version vom 6. Oktober 2022, 08:33 Uhr
Zeile 83:		Zeile 83:

	=== Compensating the cookie problem ===		=== Compensating the cookie problem ===
	[[~~File~~:~~Redirection~~.PNG \| thumb \| right \| frame \| Visualization of redirection]] The store must be called once '''standing alone'''. This allows cookies to be set and - if the customer arrives at the site via smartphone - the user has an optimal experience. After the purchase, the user is then redirected back to the website. The customer will also be redirected back if the viewport is large enough for the full view.		[[Datei:Umleitung.PNG \| thumb \| right \| frame \| Visualization of redirection]] The store must be called once '''standing alone'''. This allows cookies to be set and - if the customer arrives at the site via smartphone - the user has an optimal experience. After the purchase, the user is then redirected back to the website. The customer will also be redirected back if the viewport is large enough for the full view.

	'''So always set links to the store to the EINBAUCODE.		'''So always set links to the store to the EINBAUCODE.

Niklas: /* Installation via Iframe */

2022-10-06T06:32:10Z

Installation via Iframe

← Nächstältere Version		Version vom 6. Oktober 2022, 08:32 Uhr
Zeile 71:		Zeile 71:
	'''We need the following information for the installation:'''		'''We need the following information for the installation:'''
	* The exact URL, in which the iframe is to be inserted later		* The exact URL, in which the iframe is to be inserted later
	'''Please send us the info to info@~~weinbau-online~~.de'''		'''Please send us the info to info@winestro.cloud'''

	=== The installation link ===		=== The installation link ===

Niklas: /* Transfer of existing stores into new pages */

2022-10-06T06:16:00Z

Transfer of existing stores into new pages

← Nächstältere Version		Version vom 6. Oktober 2022, 08:16 Uhr
Zeile 50:		Zeile 50:

	=== Transfer of existing stores into new pages ===		=== Transfer of existing stores into new pages ===
	If you should revise a homepage in which a ~~Weinbau-online Shop~~ is already integrated, pay attention with the again arranged sides that certain parameters in Design and (see below) the forwarding and the CORS gändern must. Please inform us immediately about the customer (see above) by a ticket with the required information (e.g. URL of the new pages).		If you should revise a homepage in which a Winestro shop is already integrated, pay attention with the again arranged sides that certain parameters in Design and (see below) the forwarding and the CORS gändern must. Please inform us immediately about the customer (see above) by a ticket with the required information (e.g. URL of the new pages).

	=== Cookie Consent & Privacy ===		=== Cookie Consent & Privacy ===

Niklas: /* The start with the winery */

2022-10-06T06:04:58Z

The start with the winery

← Nächstältere Version		Version vom 6. Oktober 2022, 08:04 Uhr
Zeile 29:		Zeile 29:
	The process to the finished webshop looks like this:		The process to the finished webshop looks like this:

	# The winery has booked the [https://www.weinbau-online.de/preise.php ~~complete package with webshop or the premium~~ package].		# The winery has booked at least the [https://www.weinbau-online.de/preise.php base package].
	# We send the winery a quote for the store creation with a link to the [https://www.weinbau-online.de/weinbau-blog.php?id_blog_post=147 sample stores].		# We send the winery a quote for the store creation with a link to the [https://www.weinbau-online.de/weinbau-blog.php?id_blog_post=147 sample stores].
	# The winery chooses a template for the rough look and confirms the offer '''with the proposal / design template at the same time'''		# The winery chooses a template for the rough look and confirms the offer '''with the proposal / design template at the same time'''