Latest News: (loading..)

BrockleyJohn

♥Ambassador
  • Content count

    531
  • Joined

  • Last visited

  • Days Won

    19

BrockleyJohn last won the day on July 2

BrockleyJohn had the most liked content!

4 Followers

About BrockleyJohn

Profile Information

  1. The code should be inserted even if you have not opted in to Reviews in your merchant account (it just won't show anything). If you aren't seeing the code when you view the source of the page (a 'find' on GCR will go to it), then check: that the header tags module is enabled (the first setting of the module in admin) that you have filled in the merchant id that the page you are checking is in the list (the shop root eg. catalog/ will be checked as index.php) As far as I recall, header tags modules should be processed even if the sort number is not unique, but if you have already checked the above, also make sure that the sort number is different from the other header tags modules. Please let me know how you get on.
  2. oscommerce is another online shop software. If you can't get woocommerce working properly on php7 come back to us and we'll help you get oscommerce working instead!
  3. We are focussed on oscommerce on this forum. You would be better to ask your question on stackoverflow
  4. I think that is a woocommerce site. Do you also run an oscommerce site?
  5. When you create the export file in phpMyAdmin, make sure that this option is not selected: Add CREATE DATABASE / USE statement then you will have no need to edit the file. You can simply create an empty database for the new one and then import into it. If you try the import more than once for whatever reason, empty the new database yourself before trying again so you can be sure what's in it.
  6. I have seen a situation like yours where the configure.php files on the catalog side and the admin side were pointing to different databases. It is very easy when you have multiple stores and you are trying to rebuild from a disaster to get wires crossed somewhere. Double check all the settings in the configure files for database and for file paths - both physical and logical. If you have trouble with the credentials on a payment module, don't forget to check all of the other settings; there's often one that switches between a test system and live payments and it's not always obvious. Try changing catalog/includes/application_top.php so that you can see any php errors if there are any - change the setting near the top: error_reporting(E_ALL);
  7. That looks ok but your error showed that the import thought the first line read phpMyAdmin SQL Dump SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO" Are you running the import using the 'import' option in phpmyadmin? You should. Have you got the character set as UTF-8 in both the export and the import? You should. Did you open the exported file on your computer in an editor like notepad or something and then save it? This might break it. You should not. Did you try to import just products and categories into your new database at some point? This would have wiped the tables out. I'd try the following: - double-check that the database you're trying to copy from the old server really has everything in it that you want for the new server (you may be struggling to copy something that's no good anyway) - try the whole export/import from the migrated database again
  8. You seem to be losing contents from the file along the way. I would expect it to be formatted like this: -- phpMyAdmin SQL Dump -- version 4.4.10 -- http://www.phpmyadmin.net -- -- Host: 10.169.0.146 -- Generation Time: Jul 02, 2017 at 08:14 PM -- Server version: 5.7.17 -- PHP Version: 5.3.3 SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";
  9. Happy to spend the time helping, that's why we're here! It seems to me like you're most of the way there now - but starting to sound frustrated hence the suggestion of a break. Just wait till you get your hands on the admin side of the new store - once you get your head round it you'll find there's a lot of things you can change without needing a degree in rocket science.
  10. @B.C. but if you want to go ahead with the export in phpmyadmin - the options to select/deselect all apply to the whole list, but to select individual tables just click on them. Ctrl click to add/take away from the selection ...might be time for a break!
  11. @B.C. the instructions you're following might be labelled 'for dummies' but they seem overcomplicated to me. All this business of exporting and importing tables is an alternative approach to the database conversion script. If you created a copy of your live database and then ran the script on it, you're nearly done. You just need to convert from a 2.3.4 database to a 2.3.4 responsive one. Any additional things that might need doing depend on what addons you have in your 2.2 store. Additional images, for example, can be turned into 2.3.4 responsive images with a script.
  12. Call out to folks working on their own server (physical or virtual) to test this please. It needs trying out on an installation running the default server options for MySQL 5.7 which won't be the case on shared hosting.
  13. @B.C. The error is telling you are trying to create an index that already exists. It means that your database (for whatever reason) doesn't need the upgrade step that you are running. The script contains several steps that get you through all the upgrades needed to get through the three releases of osc 2.2 right up to 2.3.4 With this error, I suspect that your database is osc 2.2 RC2 That means that you don't need the first two steps in the file (the ones labelled RC1 SQL and RC2 SQL). Just delete from the beginning until the file starts ############ #2.3.0 SQL ############ and then try again.
  14. v1.2 now available in the new look addons/apps area: https://apps.oscommerce.com/Apps&8iAPs&store-times-bs
  15. Take a breath, Stefanie! I know all this stuff is frustrating. A modern version (which the official 2.3.4 isn't) won't look exactly like your familiar store because it needs to work on mobiles - half your visitors will be using them. You should be taking the BS community version everyone is talking about (Gold/Edge). Although it's not an official version, its catalog code is incorporated into the next official version (currently in beta) and we're assured there will be a migration path from Edge to one of the official releases. Customisation (addons) done in the community version will give less problem for upgrades if done properly. WSOD is probably a php version issue. Here's what I think you should do: - download the Edge version - create a subfolder in your webspace to use for trying out the new version (eg. /test) - make sure you're running php5.4 or higher in that subfolder (but not your main store or you'll break it) - create an empty database to use for your install - run the install on the new shop by visiting /test - check your new install works, and have a look at how the modules work in this version (boxes, content) - create a copy of your live database - run the migration scripts on your database copy (see answer to you here https://forums.oscommerce.com/topic/408979-upgrading-to-the-latest-version/?do=findComment&comment=1757560) - change the test config files to point at the migrated database instead - make it look how you want! ...if you have addons in 2.2 you may need to do some extra stuff to cater for them. When you get stuck, start a thread and we'll help on the detail. If I don't see it, message me.