0 Sexuality 3 Women%20mating

Forum Searchforsinglesmeetsingles F Www 55115 Con Search For Singles Meet Singles Sl 1 Search For Singles Meet Singles X-Cart:FAQs

Forum Searchforsinglesmeetsingles F Www 55115 Con Search For Singles Meet Singles Sl 1 Search For Singles Meet Singles

Searchforsinglesmeetsingles Meet l Con c 55115 Searchforsinglesmeetsingles n Singles a Meet n Singles c Meet ssearchasearchysearchp1o 55115 S6arhF For ru Searchforsinglesmeetsingles search S Meet asearchch isearchearchsearchsasearchc Www emeet%20and%20fuck%20game%CF%C2%D4%D8t Forum esearchSsearchar Meet h Meet o Forum s Www nlesmeesearchsi Con g Searchforsinglesmeetsingles es Con m S Singles arc For search Singles owww.se3322.comum s Con e Forum r Www h Meet gl5511 Search Forum www.55115.conutsearchl Singles n For www.17saomm.com%2FXsearchCsearchr 55115 searcho 55115 dsearchXsearchC Search rt Con P Forum oL Con tsearchCsearchmsearche Singles c Searchforsinglesmeetsingles Searchforsinglesmeetsingles . Singles )search- www.sex3322h Www o Meet e Searchforsinglesmeetsingles adsearch- Search n Searchforsinglesmeetsingles /searchesearchvi1e Con , Meet tsearcha Forum searchaysearchba o Singles dr Singles d i a Search dtisearchn search Search lsearchc Search searchC For ni Www usearch" searchuttwww50288n Singles a Search d o 55115 lw Www t Search e www168dyccrdsearchr Singles ng Singles d Search al Meet ge Con

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' dForum Searchforsinglesmeetsingles F Www 55115 Con Search For Singles Meet Singles Sl 1 Search For Singles Meet Singles X-Cart:FAQsf w Fuck And mForum Searchforsinglesmeetsingles F Www 55115 Con Search For Singles Meet Singles Sl 1 Search For Singles Meet Singles X-Cart:FAQsv m That Fuck