13 hours ago, mfleeson said:
Just wondering, why you are offering this when Phoenix is actually on 22.214.171.124 not 126.96.36.199 and also why you are offering this when you're don't appear to be a project developer?
Like I said, Just wondering....
The idea of my post is to have a list of certified addons and not to be a place to exchange ideas. I will create another post for that purpose.
It would be very good if you can add to the list the addons that you test and can certify that they work correctly with the version of Phoenix that is the one that was tested.
Regarding your other queries:13 hours ago, mfleeson said:
why you are offering this when Phoenix is actually on 188.8.131.52 not 184.108.40.206
As I am discriminated against accessing the Phoenix club, I have no way of updating from version 220.127.116.11 to 18.104.22.168. Unfortunately, this information is not available in the forum. Therefore I am testing the addons in 22.214.171.124 and I did not have time to test them in 126.96.36.199 or the next versions that may appear. It would be great if you can help me and test them and publish your results.13 hours ago, mfleeson said:
why you are offering this when you're don't appear to be a project developer?
It is my way of helping the Phoenix project (although I am not welcome in it). I have no commercial interest (as others have) I just want to help new users to see what addon listings exist in the market. All this information is public. I'm just ordering it for the benefit of the community.
mfleeson replied to valquiria23's topic in osCommerce Online Merchant Community Bootstrap EditionHi Valquiria Just wondering, why you are offering this when Phoenix is actually on 188.8.131.52 not 184.108.40.206 and also why you are offering this when you're don't appear to be a project developer? Like I said, Just wondering.... M
mfleeson replied to cinolas's topic in General SupportIt sounds like although you increased the length of the product_attributes you didn't change the matching order_product_attributes. Can you supply the create table sql's for your product and order tables?
The database changes in 220.127.116.11 were increasing the varchars to 255. I created an update script for Gary but he's not included it in the package. You can use the following SQL.
/* Update to existing installations adjusting VARCHARs to 255 in length */
ALTER TABLE categories
CHANGE COLUMN categories_image categories_image VARCHAR(255) NOT NULL;
ALTER TABLE categories_description
CHANGE COLUMN categories_name categories_name VARCHAR(255) NOT NULL,
CHANGE COLUMN categories_seo_keywords categories_seo_keywords VARCHAR(255) NOT NULL,
CHANGE COLUMN categories_seo_title categories_seo_title VARCHAR(255) NOT NULL;
ALTER TABLE manufacturers
CHANGE COLUMN manufacturers_name manufacturers_name VARCHAR(255) NOT NULL,
CHANGE COLUMN manufacturers_image manufacturers_image VARCHAR(255);
ALTER TABLE manufacturers_info
CHANGE COLUMN manufacturers_seo_keywords manufacturers_seo_keywords VARCHAR(255) NULL,
CHANGE COLUMN manufacturers_seo_title manufacturers_seo_title VARCHAR(255) NULL;
ALTER TABLE orders_products
CHANGE COLUMN products_model products_model VARCHAR(255),
CHANGE COLUMN products_name products_name VARCHAR(255) NOT NULL;
ALTER TABLE orders_products_attributes
CHANGE COLUMN products_options products_options VARCHAR(255) NOT NULL,
CHANGE COLUMN products_options_values products_options_values VARCHAR(255) NOT NULL;
ALTER TABLE products
CHANGE COLUMN products_model products_model VARCHAR(255),
CHANGE COLUMN products_image products_image VARCHAR(255);
ALTER TABLE products_description
CHANGE COLUMN products_name products_name VARCHAR(255) NOT NULL DEFAULT '',
CHANGE COLUMN products_seo_keywords products_seo_keywords VARCHAR(255) NULL ,
CHANGE COLUMN products_seo_title products_seo_title VARCHAR(255) NULL ;
ALTER TABLE products_images
CHANGE COLUMN image image VARCHAR(255);
ALTER TABLE products_options
CHANGE COLUMN products_options_name products_options_name VARCHAR(255) NOT NULL DEFAULT '';
ALTER TABLE products_options_values
CHANGE COLUMN products_options_values_name products_options_values_name VARCHAR(255) NOT NULL DEFAULT '';
Just a silly bit of SQL. I realised that products I had used in previous promotion were not displaying as they were not in any categories, so here's a little bit of SQL to help fix databases if you've been using other tools to administrate your products. 1 - Check for products not in categories. SELECT * FROM products WHERE products_id NOT IN (SELECT DISTINCT products_id FROM products_to_categories); 2 - If none display then you're fine. If they do then choose a category to put them in and get the category number. If need be create a new category and look for the number in the database, i.e. SELECT MAX(categories_id) FROM categories_description; 3 - Move the uncategorised products into your new category... If the previous query resulted in 211 then INSERT INTO products_to_categories SELECT products_id,211 FROM products WHERE products_id NOT IN (SELECT DISTINCT products_id FROM products_to_categories);
My version of the code includes a fallback so that if the none of the pricing works out, it assumes I will send it via courier and charges £12.99 (hermes pricing) I've almost finished updating the pricing matrix for the this years Royal Mail pricing so I'll tack it here soon.
As part of my experimentation with Phoenix, I wrote the following database script to move my current live data into Phoenix so I could see what it did. I thought I'd share it for anyone who's needing to move a live store to test or vice-versa. Any questions/comments please let me know. For this script to work, load it into your database tool and search and replace changing old_db to the name of your current live site (or origin data), select the new phoenix database and run the queries there. A couple of things I noticed moving from a 2.3.4 to Phoenix. Check your old sites categories_description table. Some older sites do not have categories_seo_description so this will fail on the select. change to '' in select. Check your manufacturers_info table for 'manufacturers_seo_description',and other seo fields and if it fails change them to '' in the select. If you get an error Data truncated for column then it means your old table has larger text length than in phoenix. Adjust phoenix field length and re-run query. A lot of old products table do not have products_gtin fields, modify field to '' in query Test Move SQL.sql
Hi I have a two versions of the Royal Mail, one for UK and one for Airmail both which work with 2.3.4 BS. I'll be looking to port them to phoenix once I'm up and running development again. Let me know if you're still interested in this being available. Cheers Mark
Tracked the issue down. My version of oscommerce is wrapped in Joomla JCommerce and in application_top is a whole load of globals. Added it to that and it worked although it came up with define errors and didn't come up with the auto-configure. Will continue to experiment. Thanks Mark
Has anyone here tried installing the new Paypal App. I'm getting an error 500 after clicking install. Traced it to Fatal error: Call to a member function getDef() on a non-object in /home/testls/public_html/2016/components/com_jcommerce/includes/apps/paypal/modules/PS/PS.php on line 24 which is trying to access a global but doesnt appear to have been defined! In the function OSCOM_PayPal_PS there is a global $OSCOM_PayPal; but it's returning null. Any ideas? Thanks Mark