Jan Zonjee

I'm sure ;you are going to tell us soon via an another account.

Looks to me that "< ? php /* */ " shouldn't be part of the SQL syntax. But what about the spaces in "< ? php" Shouldn't it be "<?php" ?

A version of Quick Price Updates has been uploaded today that is adapted for Separate Pricing Per Customer (SPPC). If you don't have this installed, don't use it! Use this thread for questions. This version is based on the Quick Price Updates version 2.6 of Februari 2005. The "only" additional feature is that you can choose a customer group and then the prices for that customer group will be shown and can then be changed. So you can only change prices for products for one particular customer group, not all at once (I don't think it is even possible). Maybe not ideal, but it might be helpful. The newer versions of Quick Price Updates all seem to cater to people with particular contributions installed, so I opted to use the latest one that was still kind of generic. The features that were already in, like selecting according to category and manufacturer (or both), sorting (sorting on price will be according to retail price) and editing of model, product status, title, tax etcetera are still in. It appears to work OK, but since this is a new version: be careful and backup your database first before using it. For the record: the contribution can be found here.

This contribution aims to get the database backup manager in osC 2.2 to work better with large databases especially on servers where safe_mode is set to on.

Yes, that would need to be changed. Would this work? : <?php echo $this->customer['customers_group_name']; ?></p> instead of: <?php echo $order->customer['customers_group_name']; ?></p>

Sounds like the best option. Haven't tried this so just writing queries from what I remember of them :-) : admin/classes/order.php around line 30: function query($order_id) { global $languages_id; $order_id = tep_db_prepare_input($order_id); $order_query = tep_db_query("select customers_id, customers_name, customers_company, customers_street_address, customers_suburb, customers_city, customers_postcode, customers_state, customers_country, customers_telephone, customers_email_address, customers_address_format_id, delivery_name, delivery_company, delivery_street_address, delivery_suburb, delivery_city, delivery_postcode, delivery_state, delivery_country, delivery_address_format_id, billing_name, billing_company, billing_street_address, billing_suburb, billing_city, billing_postcode, billing_state, billing_country, billing_address_format_id, payment_method, cc_type, cc_owner, cc_number, cc_expires, currency, currency_value, date_purchased, orders_status, last_modified from " . TABLE_ORDERS . " where orders_id = '" . (int)$order_id . "'"); $order = tep_db_fetch_array($order_query); // BOF SPPC $customer_group_query = tep_db_query("select cg.customers_group_name from " . TABLE_CUSTOMERS . " c, " . TABLE_CUSTOMERS_GROUPS . " cg on c.customers_group_id = cg. customers_group_id where c.customers_id = " . $order['customers_id'] . " "); $customer_group_info = tep_db_fetch_array($customer_group_query); // EOF SPPC and then later (around line 71 now): $this->customer = array('id' => $order['customers_id'], 'name' => $order['customers_name'], 'company' => $order['customers_company'], 'street_address' => $order['customers_street_address'], 'suburb' => $order['customers_suburb'], 'city' => $order['customers_city'], 'postcode' => $order['customers_postcode'], 'state' => $order['customers_state'], 'country' => array('title' => $order['customers_country']), 'format_id' => $order['customers_address_format_id'], // BOF SPPC 'customers_group_name' => $customer_group_info['customers_group_name'], // EOF SPPC 'telephone' => $order['customers_telephone'], 'email_address' => $order['customers_email_address']);

This is the support thread for the Admin Specials by Categories for SPPC contribution. The original contribution is Admin Specials by Categories by Carine Bruyndoncx. Since Separate Pricing Per Customer adds customer groups in the mix, it needed some changes to work with SPPC. Version 1.0 is based on version 1.4 of Carine (the version to which selection based on manufacturer was added). The SPPC version has pagination added, just in case somebody has a large number of products.

bmp is not a format normally used on webpages. http://www.htmlgoodies.com/primers/html/article.php/3478181/Basic-HTML-Images.htm Even though some browers, such as Internet Explorer, will allow you to place a BMP as an image, I wouldn't. Most browsers will not be able to display it. Go with .gif, .jpg or .png. Not a clue. Maybe too big and over the size limit PHP will allow?

This is the support thread for the "Upgrading osC from 2.2 Milestone 2 to 2.2 RC2a" contribution (addon #6654). This contribution documents and describes the changes to update a osCommerce 2.2 milestone 2 shop to the latest version (release candidate 2a). This is useful for example in case your hosting upgraded MySQL to version 5, PHP to version 5, decided to set register globals to off or you want to implement the latest bugfixes and security fixes.

Because you don't want to start with those outdated data in those tables.

Could it be you are just uploading a text file where to download a template? That's not allowed. It should be availabe/downloadable from the osC addon site.

Is that file (xsell_products.php) actually there in catalog/includes/modules/ ?

The ALL CAPITALS filenames point to missing constants. Probably, you missed adding these constants to the file admin/includes/filenames.php. Something like: define('FILENAME_GROUPS', 'groups.php');

No, but to me a number of things looks suspicious in the above piece of code. In the line: if (tep_not_null($listing['specials_new_products_price'])) { it looks like the [$x] is missing. Also there is a "del" tag in the html-code. I assume most browsers will display it as text with a line through it but the appropriate way to do it is probably using CSS like: <span style="text-decoration: line-through;">

Support thread for the Optimize Categories Box contribution.

Not a clue, but I would say, retype that character (or delete it) and try again.

Perhaps this page is helpful.

There are solutions for converting an UTF-8 file to an iso-8859-1 file because you are right, I remember this happening with text editors. But isn't it easier to start with a French language pack such as this or this one and add only the translations (for other addons) you need to those files? If you want to delete the english files you also need to remove the English language in your admin.

What is wrong with saving your french.php as iso-8859-1 (Latin 1)? As Phil explained using UTF-8 for your site needs a number of things: the webserver should use UTF-8 instead of iso-8859-1, your settings should say it is UTF-8 (probably not so important) and very important your database in this case should be set to utf-8 also as well as the content of the database should be converted to UTF-8. All in all it looks like the easiest solution in this case is to save your french.php as iso-8859-1 and forget about UTF-8.

As far as I can remember there are instructions in the contributions how to troubleshoot this by logging the outgoing message and incoming xml message.

For starters the pages you link to are not accessible: 403 Forbidden You are not allowed to access this page. Possible problems: [*]Missing index file [*]Misconfigured mod_rewrite settings in .htaccess [*]Authentication Failure [*]Incorrect file or folder permissions

Sorry, but I think the difference is so minimal it's not worth implementing (besides the security risk I when writing your database information to a file that might be read by a hacker?).

A quick search of the addons turned up two packages: Catalan Language and Catalan Language for osCommerce v2.3.1

That are settings in osCommerce itself, not in UPS XML.

Did you "install" the module in the admin too? It will show up under payment modules (if both PHP files where put in the right place) but then you still need to click a few buttons and more than likely fill out a few details before the payment module is actually shown to customers.