CasperVend 2/Quick Start: Difference between revisions
mNo edit summary |
|||
(46 intermediate revisions by 3 users not shown) | |||
Line 2: | Line 2: | ||
|__TOC__ | |__TOC__ | ||
|} | |} | ||
[[File:German_flag.gif]] [[CasperVend_2/Quick_Start/DE | Dies in deutsch!]] | |||
== '''<span style="color:#00528c">Feature List</span>''' == | |||
Want to see the capabilities first? '''[[CasperVend_2/Feature_List | Click here.]]''' | |||
== '''<span style="color:#00528c">Create Your Products</span>''' == | == '''<span style="color:#00528c">Create Your Products</span>''' == | ||
Line 13: | Line 19: | ||
: 5) If you want your shipping package to unpack on rez (or on wearing) there are third party scripts available on Marketplace or Primbay. Remember to TEST FIRST. | : 5) If you want your shipping package to unpack on rez (or on wearing) there are third party scripts available on Marketplace or Primbay. Remember to TEST FIRST. | ||
=== '''Why Do I Have to Upload My Images?''' === | |||
---- | |||
: '''Q. Why do I have to upload my images? Marketplace allows free uploads, why can't CasperVend do that?''' | |||
: '''A.''' The vendor scripts call the images via the image's UUID. You can only GET a UUID for an image, if the image has been uploaded to SL. Remember, Marketplace is run by Linden Lab, and it has its own "inventory servers" from which the images gets shown. That's why Marketplace images don't need to be an SL upload. | |||
== '''<span style="color:#00528c">Package Your Products</span>''' == | == '''<span style="color:#00528c">Package Your Products</span>''' == | ||
: 1) Each product (with its respective parts) goes in '''one''' shipping package. | : 1) Each product (with its respective parts) goes in '''one''' shipping package. | ||
: 1a) This shipping package can be a bag, a crate, whatever. It '''CANNOT''' be a folder, because the DropBox cannot deliver a folder. | |||
: 2) Add any relevant notecards, landmarks, product pictures, etc. that you want the customers to have for that product into that shipping package at this time. | : 2) Add any relevant notecards, landmarks, product pictures, etc. that you want the customers to have for that product into that shipping package at this time. | ||
: 3) Make sure each product package has its own unique name. | : 3) Make sure each product package has its own unique name. | ||
: 4) Pick up your newly named shipping package(s). | |||
: | == '''<span style="color:#00528c">Unpack CasperVend Crate & Fill Your DropBox</span>''' == | ||
: | : 1) Unpack your CasperVend shipping crate. | ||
: | : 2) Rez a copy of the CasperTech DropBox (the box, not the sphere). | ||
: | : 3) Drag your product package(s) from your inventory into the "contents" tab of the DropBox. | ||
: 4) Add your store landmark - and give it a generic name, such as '''"((your store name)) - Main Location"'''. | |||
: 5) All packages, notecards, landmarks, and any textures must ALL have unique names. This is to prevent the system from getting confused and thinking the wrong item is the product package. | |||
: '''5) Dropboxes MUST remain rezzed inworld to deliver items!''' | |||
== '''<span style="color:#00528c">Set Up Product Listings</span>''' == | == '''<span style="color:#00528c">Set Up Product Listings</span>''' == | ||
: 1) Once everything is in, and the dropbox has finished sending data up to the website, click the DropBox and select "Admin" from the popup menu. | : 1) Once everything is in, and the dropbox has finished sending data up to the website, click the DropBox and select "Admin" from the popup menu. | ||
: 2) Let it take you to the CasperVend website where you can '''[[ | : 2) Let it take you to the CasperVend website where you can '''[[Passwords_CasperVend | create your account]]''' and log in. | ||
: 3) Click "Products" on the left column. | |||
: 4) If you have no products set up already, the page will be empty. This is '''normal''' until you begin setting up products. (The "Products" page only shows '''completed''' listings.) | |||
: 5) Click the green [[File:Listnew.png||||"List New Product"]] button | |||
: 6) You will now be presented with the product setup screen for your individual product. | |||
: 7) See the '''[[CasperVend_2/Product_Options | product options]]''' page for details on how to set up products. | |||
: 8) To save space in your dropbox, for each product's vendor texture, simply right-click on the texture '''in your inworld inventory,''' select '''"copy UUID"''', and paste that in the UUID box within the product listing page. | |||
: | : 9) Remember to click "save" at the bottom when you are done filling in product information. | ||
: | : 10) Repeat for each product you want to set up at this time. | ||
: | == '''<span style="color:#00528c">Sales Notifications</span>''' == | ||
There is a link on the Overview tab to turn sales notifications on or off. | |||
By default, these notifications are on. | |||
If you are migrating a busy store to CasperVend, and you don't want these notifications cluttering your local chat buffer, simply to to your overview tab, and scroll down to the options box on the bottom of the middle column, and turn them off. | |||
: | '''NOTE:''' Disabling sales notifications '''does not''' stop failed transaction notices - this is intentional, so that you are notified of issues. | ||
== '''<span style="color:#00528c">Rez Your Vendors</span>''' == | == '''<span style="color:#00528c">Rez Your Vendors</span>''' == | ||
Line 53: | Line 88: | ||
: 2) Grant '''[[Debit_Permissions | debit permissions]]''' - the vendor will not function without them. | : 2) Grant '''[[Debit_Permissions | debit permissions]]''' - the vendor will not function without them. | ||
: 3) At this point, you will see one or more products magically appear on your inworld vendor. | : 3) At this point, you will see one or more products magically appear on your inworld vendor. | ||
: 4) The default action on click for ALL vendors is "touch" - you may, if you wish, set it to "Pay" instead. (Right-Click > Edit > "General" tab > Default Action pulldown = Pay Object). | |||
: 5) Do '''not''' use "buy", because all "buy" will do is sell your customers the MAPPING notecard and the vendor script. | |||
=== "Take a Copy" grid-based quirk === | |||
---- | |||
There's a quirk with using "Take Copy" with rental units and vendors, that you should be aware of. | |||
Because the server is unaware of this copy being made, the copy that ends up in your inventory is LINKED to the one that is still rezzed, and is NOT a proper copy. | |||
If you then modify the one that's still rezzed, the copy that you took *will change too*. | |||
To avoid this, TAKE into inventory and then REZ the copy. This will create a proper copy with its own unique UUID. | |||
=== How do I put my textures on the vendor? === | |||
---- | |||
: If you are using the "Headless" vendor, just apply the texture right to the vendor inworld. | |||
: If you are using any other type of panel vendor, add the texture UUID to the product listing on the website. | |||
=== What size should I make the texture? === | |||
---- | |||
: We '''*RECOMMEND*''' no larger than 512 x 512 for viewing on the vendor. This allows the texture to load quickly for most people. | |||
: While you can upload larger filesize textures, keep in mind that if your texture won't load for the customer (not everyone has high broadband and state-of-the-art computers), customers are NOT likely to buy. It's to your advantage to keep the filesize small, to make them load quickly. | |||
=== But I just want to use my existing vendor prims! === | |||
---- | |||
No scripting is required to use your own vendor objects! | |||
If you are using something equivalent to the behavior of a "buy box", and just want to convert that to CasperVend, use the "Headless Vendor" box, and see '''[https://wiki.casperdns.com/images/1/1a/Flowchart_for_using_existing_vendor_objects.png this flowchart]''' for the process overview. | |||
== '''<span style="color:#00528c">Adding New Products</span>''' == | |||
: Use the same steps above that you used to create your initial products and listings. | |||
== '''<span style="color:#00528c">Show Specific Product(s) On Specific Vendor(s)</span>''' == | == '''<span style="color:#00528c">Show Specific Product(s) On Specific Vendor(s)</span>''' == | ||
Line 59: | Line 130: | ||
If you want to have only certain products showing on a specific multi-panel vendor, you will need to set up - and use - '''[[CasperVend_2/Profiles_and_groups | profiles]]'''. | If you want to have only certain products showing on a specific multi-panel vendor, you will need to set up - and use - '''[[CasperVend_2/Profiles_and_groups | profiles]]'''. | ||
== '''<span style="color:#00528c">Vendor Configuration - Profiles</span>''' == | == '''<span style="color:#00528c">Vendor Configuration - Profiles (Multi-Product)</span>''' == | ||
Once you have your profiles set up, it's time to attach the appropriate profile to the appropriate vendor. | Once you have your profiles set up, it's time to attach the appropriate profile to the appropriate vendor. | ||
Line 71: | Line 142: | ||
: 4) Select the profile, and click "save". | : 4) Select the profile, and click "save". | ||
: 5) Page will process, and the appropriate profile will appear on the multi-panel vendor. | : 5) Page will process, and the appropriate profile will appear on the multi-panel vendor. | ||
== '''<span style="color:#00528c">Vendor Configuration - Single Product</span>''' == | == '''<span style="color:#00528c">Vendor Configuration - Single Product</span>''' == | ||
Line 84: | Line 155: | ||
: 5) Page will process, and the selected product will appear on the vendor inworld. | : 5) Page will process, and the selected product will appear on the vendor inworld. | ||
=== Single Item Vendor Types === | |||
---- | |||
All vendors - single or multi product - will rez out and '''by default''' will pull in what is called the "default" profile. However, the vendors in this list do not have arrows, and will need to be specifically told which single product you want to be shown on that vendor: | |||
:* Touch vendor | |||
:* Two-faced | |||
:* Headless | |||
:* Static | |||
== '''<span style="color:#00528c">How do I....?</span>''' == | == '''<span style="color:#00528c">How do I....?</span>''' == | ||
:* ...set up '''[[CasperVend_2/Affiliates | affiliate vendors]]''' | :* ...set up '''[[CasperVend_2/Affiliates | affiliate vendors]]''' | ||
:* ...set your vendors for a '''[[CasperVend_2/Customers_Page | | :* ...set your vendors for a '''[[CasperVend_2/Customers_Page | grid-wide sale]]''' | ||
:* ...link your '''[[CasperVend_2/Marketplace_Link | Marketplace via ANS]]''' (Marketplace store owner name MUST match CasperVend system owner name) | :* ...link your '''[[CasperVend_2/Marketplace_Link | Marketplace via ANS]]''' (Marketplace store owner name MUST match CasperVend system owner name) | ||
:* ...keep '''[[CasperVend_2/DropBoxes#When_Possible.2C_Have_Duplicate_DropBox.28es.29 | backup dropboxes]]''' in case of sim/region failure | :* ...keep '''[[CasperVend_2/DropBoxes#When_Possible.2C_Have_Duplicate_DropBox.28es.29 | backup dropboxes]]''' in case of sim/region failure | ||
:* ...import your sales data from '''[[CasperVend_2/CSV_Import | other supported vending systems]]''' | :* ...import your sales data from '''[[CasperVend_2/CSV_Import | other supported vending systems and prior Marketplace sales]]''' | ||
:* ...sell textures, if you have the TextureVend pack. See the '''[[CasperVend_2/TextureVend | TextureVend page]]''' for details. | :* ...sell textures, if you have the TextureVend pack. See the '''[[CasperVend_2/TextureVend | TextureVend page]]''' for details. | ||
:* ...rez demos, if you have the HoloVend pack. See the '''[[CasperVend_2/Holovendors | holovendors page]]''' for details. | :* ...rez demos, if you have the HoloVend pack. See the '''[[CasperVend_2/Holovendors | holovendors page]]''' for details. | ||
Line 99: | Line 179: | ||
== '''<span style="color:#00528c">FAQ / Troubleshooting</span>''' == | == '''<span style="color:#00528c">FAQ / Troubleshooting</span>''' == | ||
: '''Q. "Currently logged in user has no access to configure this vendor" but they're MY vendors! | |||
:: '''A1.''' This is because the vendor used to have a different type of script that the one that is inside the vendor now. | |||
:: '''A2.''' The fix is: | |||
:::* (1) Remove contents of description field, and hit return. | |||
:::* (2) Shift-drag a new copy. | |||
:::* (3) Grant perms on the new copy (the one left behind when dragging.) | |||
:::* (4) Delete the old copy (the one you dragged.) | |||
:::* (5) Use the NEW copy. | |||
: '''Q. I'm setting up my vendors, but they're not booting up and I don't see the debit perm windows!''' | : '''Q. I'm setting up my vendors, but they're not booting up and I don't see the debit perm windows!''' | ||
:: '''A1.''' Vendors don't finish the boot process because they're waiting for you to grant debit permissions. If you are using a v3 viewer, they can accumulate behind a tiny "chicklet toast" in the corner of your screen. Check the upper right and the lower right to see if they're hanging out there waiting for you to answer. | :: '''A1.''' Vendors don't finish the boot process because they're waiting for you to grant debit permissions. If you are using a v3 viewer, they can accumulate behind a tiny "chicklet toast" in the corner of your screen. Check the upper right and the lower right to see if they're hanging out there waiting for you to answer. | ||
:: '''A2.''' All viewer3-style viewers actually '''store''' your popup notifications, unless you dismiss them. Over time, undismissed notifications build up - if you have too many, you may not be able to log in, '''OR''' you may not actually '''SEE''' any new notifications '''at all'''. You can see details of the problem AND the fix over on the '''[http://wiki.phoenixviewer.com/fs_install_crash Firestorm wiki]'''. | :: '''A2.''' All viewer3-style viewers actually '''store''' your popup notifications, unless you dismiss them. Over time, undismissed notifications build up - if you have too many, you may not be able to log in, '''OR''' you may not actually '''SEE''' any new notifications '''at all'''. You can see details of the problem AND the fix over on the '''[http://wiki.phoenixviewer.com/fs_install_crash Firestorm wiki]'''. |
Latest revision as of 14:28, 11 September 2022
Feature List
Want to see the capabilities first? Click here.
Create Your Products
- 1) Create your products for sale. If your products are items to be rezzed (like furniture or buildings), remember to set the next-owner permissions while they are rezzed inworld.
- 2) Create the pictures to be used for your vendors and upload them to SL.
(The vendors will call the image by the UUID, and there is no UUID if the image hasn't been uploaded to SL.)
- 3) Create your shipping package. You cannot use folders with CasperVend - the dropbox is only capable of sending packaged products.
(box, bag, crate, whatever you want to be seen when your customers unpack everything.)
- 4) If your items need to be rezzed anyway, simply right-click > edit > general tab > set default action to "open" on click.
- 5) If you want your shipping package to unpack on rez (or on wearing) there are third party scripts available on Marketplace or Primbay. Remember to TEST FIRST.
Why Do I Have to Upload My Images?
- Q. Why do I have to upload my images? Marketplace allows free uploads, why can't CasperVend do that?
- A. The vendor scripts call the images via the image's UUID. You can only GET a UUID for an image, if the image has been uploaded to SL. Remember, Marketplace is run by Linden Lab, and it has its own "inventory servers" from which the images gets shown. That's why Marketplace images don't need to be an SL upload.
Package Your Products
- 1) Each product (with its respective parts) goes in one shipping package.
- 1a) This shipping package can be a bag, a crate, whatever. It CANNOT be a folder, because the DropBox cannot deliver a folder.
- 2) Add any relevant notecards, landmarks, product pictures, etc. that you want the customers to have for that product into that shipping package at this time.
- 3) Make sure each product package has its own unique name.
- 4) Pick up your newly named shipping package(s).
Unpack CasperVend Crate & Fill Your DropBox
- 1) Unpack your CasperVend shipping crate.
- 2) Rez a copy of the CasperTech DropBox (the box, not the sphere).
- 3) Drag your product package(s) from your inventory into the "contents" tab of the DropBox.
- 4) Add your store landmark - and give it a generic name, such as "((your store name)) - Main Location".
- 5) All packages, notecards, landmarks, and any textures must ALL have unique names. This is to prevent the system from getting confused and thinking the wrong item is the product package.
- 5) Dropboxes MUST remain rezzed inworld to deliver items!
Set Up Product Listings
- 1) Once everything is in, and the dropbox has finished sending data up to the website, click the DropBox and select "Admin" from the popup menu.
- 2) Let it take you to the CasperVend website where you can create your account and log in.
- 3) Click "Products" on the left column.
- 4) If you have no products set up already, the page will be empty. This is normal until you begin setting up products. (The "Products" page only shows completed listings.)
- 6) You will now be presented with the product setup screen for your individual product.
- 7) See the product options page for details on how to set up products.
- 8) To save space in your dropbox, for each product's vendor texture, simply right-click on the texture in your inworld inventory, select "copy UUID", and paste that in the UUID box within the product listing page.
- 9) Remember to click "save" at the bottom when you are done filling in product information.
- 10) Repeat for each product you want to set up at this time.
Sales Notifications
There is a link on the Overview tab to turn sales notifications on or off.
By default, these notifications are on.
If you are migrating a busy store to CasperVend, and you don't want these notifications cluttering your local chat buffer, simply to to your overview tab, and scroll down to the options box on the bottom of the middle column, and turn them off.
NOTE: Disabling sales notifications does not stop failed transaction notices - this is intentional, so that you are notified of issues.
Rez Your Vendors
- 1) Choose a vendor style from the CasperVend folder and rez it out.
- 2) Grant debit permissions - the vendor will not function without them.
- 3) At this point, you will see one or more products magically appear on your inworld vendor.
- 4) The default action on click for ALL vendors is "touch" - you may, if you wish, set it to "Pay" instead. (Right-Click > Edit > "General" tab > Default Action pulldown = Pay Object).
- 5) Do not use "buy", because all "buy" will do is sell your customers the MAPPING notecard and the vendor script.
"Take a Copy" grid-based quirk
There's a quirk with using "Take Copy" with rental units and vendors, that you should be aware of.
Because the server is unaware of this copy being made, the copy that ends up in your inventory is LINKED to the one that is still rezzed, and is NOT a proper copy.
If you then modify the one that's still rezzed, the copy that you took *will change too*.
To avoid this, TAKE into inventory and then REZ the copy. This will create a proper copy with its own unique UUID.
How do I put my textures on the vendor?
- If you are using the "Headless" vendor, just apply the texture right to the vendor inworld.
- If you are using any other type of panel vendor, add the texture UUID to the product listing on the website.
What size should I make the texture?
- We *RECOMMEND* no larger than 512 x 512 for viewing on the vendor. This allows the texture to load quickly for most people.
- While you can upload larger filesize textures, keep in mind that if your texture won't load for the customer (not everyone has high broadband and state-of-the-art computers), customers are NOT likely to buy. It's to your advantage to keep the filesize small, to make them load quickly.
But I just want to use my existing vendor prims!
No scripting is required to use your own vendor objects!
If you are using something equivalent to the behavior of a "buy box", and just want to convert that to CasperVend, use the "Headless Vendor" box, and see this flowchart for the process overview.
Adding New Products
- Use the same steps above that you used to create your initial products and listings.
Show Specific Product(s) On Specific Vendor(s)
If you want to have only certain products showing on a specific multi-panel vendor, you will need to set up - and use - profiles.
Vendor Configuration - Profiles (Multi-Product)
Once you have your profiles set up, it's time to attach the appropriate profile to the appropriate vendor.
- 1) To get to the vendor's configuration page, click the main (usually the largest, or the most centered) panel on the vendor, and select "admin" from the popup menu.
- 2) That will take you to the specific configuration page for that vendor.
- 3) Use the "Change" link on the profile line, and use the pulldown to select the profile for that vendor.
- 4) Select the profile, and click "save".
- 5) Page will process, and the appropriate profile will appear on the multi-panel vendor.
Vendor Configuration - Single Product
- 1) To get to the vendor's configuration page, click the main (usually the largest, or the most centered) panel on the vendor, and select "admin" from the popup menu.
- 2) That will take you to the specific configuration page for that vendor.
- 3) Down at the bottom of the configuration options, there's a pulldown bar right above the column of product pictures.
- 4) Click that, and select the single product you want on that vendor.
- 5) Page will process, and the selected product will appear on the vendor inworld.
Single Item Vendor Types
All vendors - single or multi product - will rez out and by default will pull in what is called the "default" profile. However, the vendors in this list do not have arrows, and will need to be specifically told which single product you want to be shown on that vendor:
- Touch vendor
- Two-faced
- Headless
- Static
How do I....?
- ...set up affiliate vendors
- ...set your vendors for a grid-wide sale
- ...link your Marketplace via ANS (Marketplace store owner name MUST match CasperVend system owner name)
- ...keep backup dropboxes in case of sim/region failure
- ...import your sales data from other supported vending systems and prior Marketplace sales
- ...sell textures, if you have the TextureVend pack. See the TextureVend page for details.
- ...rez demos, if you have the HoloVend pack. See the holovendors page for details.
When you are ready to take full advantage of the many additional options in CasperVend, see the complete user manual.
If you need help with your CasperVend system, please see Getting Help for information on how to get in touch with us.
FAQ / Troubleshooting
- Q. "Currently logged in user has no access to configure this vendor" but they're MY vendors!
- A1. This is because the vendor used to have a different type of script that the one that is inside the vendor now.
- A2. The fix is:
- (1) Remove contents of description field, and hit return.
- (2) Shift-drag a new copy.
- (3) Grant perms on the new copy (the one left behind when dragging.)
- (4) Delete the old copy (the one you dragged.)
- (5) Use the NEW copy.
- Q. I'm setting up my vendors, but they're not booting up and I don't see the debit perm windows!
- A1. Vendors don't finish the boot process because they're waiting for you to grant debit permissions. If you are using a v3 viewer, they can accumulate behind a tiny "chicklet toast" in the corner of your screen. Check the upper right and the lower right to see if they're hanging out there waiting for you to answer.
- A2. All viewer3-style viewers actually store your popup notifications, unless you dismiss them. Over time, undismissed notifications build up - if you have too many, you may not be able to log in, OR you may not actually SEE any new notifications at all. You can see details of the problem AND the fix over on the Firestorm wiki.