55115.con Realitykines%2Fcom

Forum Searchforsinglesmeetsingles H Kissing I 1 For Szh 1 Search For Singles Meet Singles X-Cart:FAQs

Forum Searchforsinglesmeetsingles H Kissing I 1 For Szh 1 Search For Singles Meet Singles

Kissing . For A Kissing tm For t For c Forum i For ssearchasearchl For tsearchosearch Forum ia Forum X Forum C For r searchd Szh isearch. Forum - Szh Sv For Fsearchru hsearch z Kissing Kissing Kisinsearch Searchforsinglesmeetsingles Szh searchse Szh rc Searchforsinglesmeetsingles r searcho Forum h 1o Forum x Szh easearchch Kissing esearch Foru Forum c Fo o Searchforsinglesmeetsingles hsearch Szh asearchc Forum asearch Kissing searchisearche Searchforsinglesmeetsingles search Singles: 调情人生（Flirt Up Your Life）o For searchnt Forum hsearch For d Searchforsinglesmeetsingles i Szh REGULAR+GALLERY+No%2E414+%B4%BAr Searchforsinglesmeetsingles a Searchforsinglesmeetsingles awww.se3322.comdsearchg Kissing tsearch h Forum Szh P For tsearchh Searchforsinglesmeetsingles U Forum g Searchforsinglesmeetsingles a Kissing esearch sec Szh io Forum . Searchforsinglesmeetsingles - insearchsc Szh i Searchforsinglesmeetsingles n'www.17saomm.comppl Forum searchasearchc For ' Kissing Szh esearchecsearch o For rafil Forum searchy searchliaki Forum gsearcho Szh Brosearchsesearch Forum usearchtsearchn Szh Szh lwww.se3322.comck Searchforsinglesmeetsingles Ap Searchforsinglesmeetsingles l' Szh

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.

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.

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.

You may want to use 'Search-and-modify' feature: - open 'modify product' page; - check 'Select-and-modify' check-box and make a search for products; - in the 'product details' section, tick boxes near necessary settings, change the values and save.

As a result the change will be applied to all the found products at once.

You should modify the '/customer/main/welcome.tpl' file. Comment out this part of the code:

{}

i.e. change it to

{}

This will hide the 'Featured products' section.

Webmaster mode allows you to edit templates within the admin interface. You may edit language variables (denoted as "$lng.XXX" in templates) by changing those values in WYSIWYG mode.

1) Before entering webmaster mode, close any template windows & label windows. Enter your admin zone, go to the 'Administration' menu, 'Webmaster mode' page. Click on 'Start webmaster mode' button.

2) The additional "templates" window will appear. It displays the list of templates composing a current page. You can call the template editor from this window by clicking a template.

3) Go to the page you want to change. To define the right template, look at the browser status line (at the page bottom). When the mouse is pointing at some text, this status line indicates the corresponding template and label.

4) To change a label, click on it. If the label is under a hyperlink, move the mouse over it and press "e" (Edit) on the keyboard. The label dialog will appear.

5) After you set a new label content you can (a)preview the site with the changed label, (b)save the text in the database, and (c)copy the label name into the clipboard (IE only).

6) The webmaster mode is based on sessions: it applies only to the computer it has been set up on. I.e., when the 'Webmaster mode' is launched, it isn't displayed at the customer's end and doesn't affect the store performance. The changes will show up only after the admin clicks on 'save' button.

7) To quit the webmaster mode, go to admin zone, to the 'Administration' menu, 'Webmaster mode' page. Click on "Quit webmaster mode" button.

NOTE: Webmaster mode will not work with compiled templates.

You can use the below SQL query to mark up all the product prices, let's say 20%:

UPDATE xcart_pricing SET price=price*1.2;

The query can be applied on "Patch/Upgrade" page in X-Cart admin back-end:

index.php?title=X-Cart:Applying_Patches#Applying_SQL_Patches

After the patch is applied, please force (re)generation of cache files and quick tables via the 'Summary/Tools' section of your store's Admin area.

NOTE: It is recommended to back up your X-Cart database before applying SQL patches.

We welcome any kind of feedback (positive or negative) about our product as valuable information that can help us to improve it.

We welcome you to share your X-Cart experience with other people on the following web-sites:

• HotScripts
• Toptenreviews
• Shopping cart reviews

Please answer the following questions in your review of X-Cart:

• What was your 1st impression of X-Cart?
• What was your impression of X-Cart after you passed the learning curve?
• Is it making your life/profession easier or harder somehow?
• What do you value most about X-Cart?
• What do you dislike most about X-Cart?
• If your web-site is live now can you say that X-Cart helps you to increase your sales?

• Try to search this website for the solution.
• Try to find out more about the problem, see How to debug X-Cart or see the section below for information on how to contact Qualiteam engineers and other knowledgeable users.

Bugs should be posted on:

• "Communication center"->"Report a bug" tab under your Qualiteam account
• span> (used during beta-testing stage)

Feature requests should be posted on span>

If possible please search the database prior to posting, to avoid creating duplicate entries.

• Post a message at span> (you must have a Qualiteam account to do that)
• Submit a ticket to the Helpdesk under your Qualiteam Account

1. If you can log in to your X-Cart admin area using another account, please do so, and reset/modify the other admin password as needed.

2. If you cannot remember your admin password, there's still hope.

The first thing you can try is to click the "Forgot password?" link from the admin area home page, for example:

xcart/admin/home.php

or just go straight to the Password Recovery page, for example:

xcart/admin/help.php?section=Password_Recovery

Enter the admin username and email address, then submit the form. Your account information will be mailed to you shortly.

3. If for some reason that doesn't work for you, you can create a temporary admin account in order to log in.

Open your phpMyAdmin (supplied by your hosting company), click the "SQL" tab and run this query:

X-Cart Gold edition

DELETE FROM xcart_customers WHERE admin_name = 'mytempadmin';
INSERT INTO xcart_customers (login, password, usertype)
VALUES ('mytempadmin', 'mytempadmin', 'P');

X-Cart Pro edition

DELETE FROM xcart_customers WHERE admin_name = 'mytempadmin';
INSERT INTO xcart_customers (login, password, usertype)
VALUES ('mytempadmin', 'mytempadmin', 'A');

You should now be able to log in using the following details:

• Username: mytempadmin
• Password: mytempadmin