1 Search For Singles Meet Singles 0

Www Searchforsinglesmeetsingles T A Teemegirls No 1 Search For Singles Meet Singles X-Cart:FAQs

Www Searchforsinglesmeetsingles T A Teemegirls No 1 Search For Singles Meet Singles

searchfsearchy Searchforsinglesmeetsingles u Teemegirls nsearchesearch searchd Www s Www a Teemegirls c Searchforsinglesmeetsingles p Www searchw Teemegirls search0c Www e Teemegirls r Www hsearchee Www ir Www sWWW.HIJAPf Teemegirls Se Teemegirls rwww.5555se.comhfo Teemegirls ssearchn Searchforsinglesmeetsingles les Teemegirls esearchtsi Www g%CA%B5%BF%F6%D7%E3%C7%F22011your+video+carde Teemegirls Searchforsinglesmeetsingles w Teemegirls U1 Www h Searchforsinglesmeetsingles psearchisearchg Www m Searchforsinglesmeetsingles tao Www s Teemegirls y Searchforsinglesmeetsingles u Www c Searchforsinglesmeetsingles n Teemegirls csearche Searchforsinglesmeetsingles t Www Www hsearchmsearchma Searchforsinglesmeetsingles u Www l Searchforsinglesmeetsingles y Www searcho Teemegirls tsearch Www hea Www msearchn Www a1ksearchnsearch,1n Www s Searchforsinglesmeetsingles ;"Management" menu, 'Shipping methods' page and add new methods in the "Defined shipping methods" section.

Does X-Cart support recurring billing?

Yes, X-Cart has Subscriptions module that allows setting up recurring billing.

How to setup X-Cart in PCI-DSS compliant manner?

Please find guidelines at X-Cart:PCI-DSS implementation guide.

Are there translations available for X-Cart?

Yes, you could find some at:

Where do I edit my "About our site", "Terms & Conditions", "Privacy statement" pages?

The pages in question are embedded static pages.

The content of these pages can be edited on the 'Static pages' page in your X-Cart admin area, for example:

xcart/admin/pages.php

REPLACE INTO xcart_config SET name='do_not_show_adv', value='Y', defvalue='', variants='';









Licensing











What is the one-license-one-store rule ?










This means that you are permitted to use one instance (a single installation) of the X-Cart software on one web server and one website only; in the event You intend to use the Software or any part thereof on more than one website, the license for each such multiple use must be obtained.










Examples explaining the one-license-one-store rule:











  1. If your store is accessible from multiple domains but the content is the same for each link, this is OK and does not require multiple licenses.









  2. If your store is accessible from multiple domains but each domain shows a different storefront skin style, this is OK and does not require multiple licenses.









  3. If your multiple stores are located at sub-domains or in sub-directories of the same domain, the license for each store is required.









  4. If your store is accessible from multiple domains and your store is customized to show/hide/alter certain part of content based on the domain, the license for each domain is required. In this situation the stores appear to have separate content thereby making them separate stores in the eyes of the license agreement. The content needs to be the same for each domain in order to qualify as a single store.










How to transfer the license to another party?










X-Cart License agreement allows you to transfer your license to another party. Read how to submit a request to transfer your license.






Licensing

What is the one-license-one-store rule ?

This means that you are permitted to use one instance (a single installation) of the X-Cart software on one web server and one website only; in the event You intend to use the Software or any part thereof on more than one website, the license for each such multiple use must be obtained.

Examples explaining the one-license-one-store rule:

  1. If your store is accessible from multiple domains but the content is the same for each link, this is OK and does not require multiple licenses.
  2. If your store is accessible from multiple domains but each domain shows a different storefront skin style, this is OK and does not require multiple licenses.
  3. If your multiple stores are located at sub-domains or in sub-directories of the same domain, the license for each store is required.
  4. If your store is accessible from multiple domains and your store is customized to show/hide/alter certain part of content based on the domain, the license for each domain is required. In this situation the stores appear to have separate content thereby making them separate stores in the eyes of the license agreement. The content needs to be the same for each domain in order to qualify as a single store.

How to transfer the license to another party?

X-Cart License agreement allows you to transfer your license to another party. Read how to submit a request to transfer your license.

How to obtain an additional license?

You can purchase an additional license in your Help Desk account, "Buy products/services" section:

- click on a necessary product link (X-Cart Gold/X-Cart Pro/LiteCommerce 2.1) - choose add-ons/services, that may be ordered in addition; - click "Continue" button and follow the ordering dialogue.

My store was moved to another domain. Is there anything that I must do pertaining to licensing?

You should change the license URL in your 

  • hit 'Change URL' button.
  • When the records are updated you will be notified by a message (in one business day maximum).

    Upgrading

    How to upgrade my store?

    Common instructions on the upgrading process can be found at X-Cart:Upgrading page.

    How to install patches manually?

    Diff file (or a patch) is a file 'describing' changes which needs to be applied to the file. In UNIX world diff files are a standard way to apply changes/fixes to a program source code. There is a special program called 'patch' which reads diff files and applies the changes to the source code. In everyday use diff files are frequently called 'patches' which may sometimes cause confusion.

    An example of diff file:

    Code:

    Index: admin/category_modify.php
    @@ -160,7 +160,7 @@
    db_query("update $sql_tbl[categories] set category='$category_name', description='$description',
    meta_tags='$meta_tags', avail='$avail', order_by='$order_by', membership='$cat_membership' where
    categoryid='$cat'");
    db_query("UPDATE $sql_tbl[categories] SET membership='$cat_membership' WHERE category LIKE
    '$category_name/%'");

    - db_query("UPDATE $sql_tbl[categories] SET
    category=CONCAT_WS('','$category_name',SUBSTRING(category,".strlen($old_category_name).")) WHERE category LIKE
    'Books/%'");
    + db_query("UPDATE $sql_tbl[categories] SET
    category=CONCAT_WS('','$category_name',SUBSTRING(category,".(strlen($old_category_name)+1).")) WHERE category
    LIKE '$old_category_name/%'");
    }

    #

    We suggest three methods for patch installation.

    1. Automatic installation via X-Cart admin. - Save the text of the patch as a file. - Log in to the admin area and go to the 'Patch/Upgrade' section. - in section 'Apply patch', select your file by clicking on 'Browse' button. Click 'Apply'.

    2. Runing 'patch' command. - Save the text of the patch as a file (e.g. patch.diff). - Copy this file (patch.diff) to the directory where your X-Cart is installed. - check the patch adaptability: if you are on Linux OS, run command 'patch --dry-run < patch.diff'; if you are on FreeBSD, run command 'patch -C < patch.diff'. - If there are no errors, apply the patch by issuing command 'patch < patch.diff'.

    Learn more about 'patch' command in the manual (man patch, info patch). If the patch fails in the first two cases, it might be caused by redundant spaces or conversion problems.

    3. Incorporate the changes right in the source code. Open the diff file in a text editor. Diff files are divided into parts ("hunks"). Each "hunk" starts with a line like this:

    @@ -160,7 +160,7 @@

    where:

    160 - indicates the first line of the code that needs to be changed 7 - indicates the number of the lines in the hunk before patch applying 7 - indicates the number of the lines in the hunk that will be after the patch is applied

    Under 'Index:' you will find the name of the file that you should patch. In our example, it is "admin/category_modify.php" Then follows the file code marked with "+" and "-" signs: Lines marked with "+" are the lines that you need to add in the file Lines marked with "-" are the lines that you need to remove from the file

    If you still fail to apply the patch, it might mean that the files to patch are modified or from another X-Cart version thus cannot be patched by this patch. Feel free to contact our support team for help.

    There are upgrade patches in my file area, what are they for and how can I use them?

    Starting with v3.2.0 a special upgrade engine, allowing upgrading to a newer version, was implemented in X-Cart. Detailed instructions on how to perform upgrades come in the upgrade packages in UPGRADE.readme files.

    Upgrade patches are a set of files which describe differences in code between old and new versions. All the changes are represented in standard diff format (UNIX unified diff format). Diff files contains structured data indicating what pieces of code are to be added/replaced/deleted: a sample of old code and a new code to insert instead. You will find more information about diff file at manual/diffutils-2.8/html_chapter/diff_toc.html

    The main advantage of this approach is that diff patch technique allows upgrading even customized versions of X-Cart: X-Cart upgrade engine follows the list of files from the file file.lst and tries to patch them. Then database upgrade is fulfilled. If the code is not changed the upgrade will be successfully completed. However, since X-cart is highly customizable product most of X-cart users are certain to modify its code and templates to meet their needs. Here might come difficulties. If a piece of the code to be patched was customized (altered), the patch engine won't patch it and the upgrade script may fail. You will be notified about it by the system. So if you have ever changed X-Cart code you should be prepared to resolve the conflicts manually.

    X-cart patch engine creates a log file that reflects a progress of the patching process - templates_c/upgrade/patch.log. The failed hunks are stored in reject files filename.ext.rej. Using this information you can figure out what parts of code haven't been patched in order to patch them manually afterwards.

    For more information on the upgrade procedure and the instructions, refer to the manual included into the upgrade archive.

    Why I'm getting checksum errors during upgrade?

    Firstly, if you use WinZip to extract files from the upgrade/distribution kit, you need to change the default configuration in the following way: Click Options,Configuration, select the Miscellaneous tab and remove the tick from 'TAR file smart CR/LF conversion'. After that unpack the files from the archive once again and re-upload the files to your server.

    Secondly, when you use FTP for uploading text files on the server it may alter your files (if it's in 'ASCII'/'Text' mode). It replaces the line-break symbols that are different for Unix and Windows systems whereas all the other text is left the same. These changes are not visible, but X-Cart checks files checksum and the values appear different from the expected ones. In order to solve the problem you should set your FTP client in the 'Binary' mode and re-upload the upgrade package files on the server.

    cWww Searchforsinglesmeetsingles T A Teemegirls No 1 Search For Singles Meet Singles X-Cart:FAQsg j Women%20mating Search For Singles Meet Singles Instruction rWww Searchforsinglesmeetsingles T A Teemegirls No 1 Search For Singles Meet Singles X-Cart:FAQsh Sites Movie