The site won't let me message you, so here's what I tried to send:
I've disabled login so you should be able to get straight in. If you click on Products and then edit an existing you can see how Harald used variants on the Dymo. If you want to access the raw product attributes component then check it out under Mark's Debug Menu!
I've backed up the database so if anything goes wrong I can always restore it.
- Show previous comments 1 more
Try this link:
Hi Fredi I've been using and developing for Oscommerce since it's inception. Due to it's limitations I moved to using oscMax and ended up being a developer on that project. I came back to Osc 2.3.4BS when I needed code that would work with updated php. I'm currently writing code for 220.127.116.11 that works within the confines of the current core. I just wondered why this forum section was restricted to 18.104.22.168 when phoenix is really rising from the ashes of the code of oscommerce and seeing modern coding standards applied. It was just a simple question/answer post. Best Wishes M
Hi Jc. Not missing the point, I was one of the developers on oscMAX a spin off from the original Oscommerce and understand about public domain software and I've run it my own store since the early 90's. I was more concerned about the disparate groups of development going on and the idea that one could authenticate 'addons' over another. Just trying to see what was going on. M
mfleeson replied to hyepo's topic in General SupportI found it on the other forum. Many thanks for the file. All ipn's are now working. Cheers. M
Thanks so much for this thread guys. I started having issues with paypal payments not coming through and I've been chasing all around the place trying to find the issue. The old version was missing both DigiCert High Assurance EV Root CA and DigiCert Global Root G2 (SHA-256) I ran araxis merge on the phoenix 22.214.171.124 cert and the one downloaded from here and they're identical. Thank you. Can I suggest this gets made as an announcement in the forums so people know to update. On a slightly different issue my Paypal app says its version 5.0.10 and then pops up An update is available for this App! . Clicking the button does nothing and from what I can see on the forum it's the latest version. Anyone got ideas? Cheers Mark
mfleeson replied to hyepo's topic in General SupportI'm having the same issue, i receive a payment email from paypal but it doesn't call back to the website.
13 hours ago, mfleeson said:
Just wondering, why you are offering this when Phoenix is actually on 126.96.36.199 not 188.8.131.52 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 184.108.40.206 not 220.127.116.11
As I am discriminated against accessing the Phoenix club, I have no way of updating from version 18.104.22.168 to 22.214.171.124. Unfortunately, this information is not available in the forum. Therefore I am testing the addons in 126.96.36.199 and I did not have time to test them in 188.8.131.52 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.
Hi Valquiria Just wondering, why you are offering this when Phoenix is actually on 184.108.40.206 not 220.127.116.11 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 18.104.22.168 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