Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation on 05/17/2019 in all areas

  1. 1 point
    MrPhil

    PHP and MySQL upgrade for 2.3.4

    1. Jumping code from PHP 5.4 to PHP 7.2 compatibility is a huge task. Even the bleeding edge Frozen and Edge work has barely started on it. They're both currently up to PHP 7.1, if you can roll back to that. If you want to do it yourself, I suggest you read https://www.php.net/manual/en/migration70.deprecated.php and for 71 and 72 as well. You might even have to take a look at 56, 55, and 54 migrations. 2. Not really. The official 2.3.4.1 is merely 2.3.4 with the PHP 7 deprecated warnings turned off. Don't use it. 3. No. The "upgrade" hits only a couple or so files, and is easy enough to do in-place. Just compare 2.3.4 and 2.3.4.1 files and you'll see. At best, turning off PHP 7 deprecated warnings will buy you a little time for a more permanent fix -- there's no telling what's not working right behind the curtain. One thing I hope you'll learn from all this is to keep your store on the current code base! This means carefully logging every single change you make to the files, what add-ons you installed, and very importantly, why you made a group of changes. There's no point in trying to replicate a bunch of code changes, only to realize half way through that Bootstrap responsive is already built in to the product! Whenever the pain of maintaining your current store's code base becomes too much, it's then easy to migrate to the latest and greatest, replicating all your new features without too much strain.
  2. 1 point
    Hello Ed @edo.script, Point 1: It looks like you tried to install/update PWA 3.0.5 over the old GOLD version from @De Dokta. It also seems you are mixing code provided from older PWA 2.x versions with PWA 3.0.5. The code you mention under point 1 is not used any more in PWA 3.0.5. Please complete uninstall your old PWA version before installing PWA 3.0.5, there are no update instructions available for that old version. For the hook call in checkout_process.php: $OSCOM_Hooks->call('pwa', 'PwaCheckoutMailMod');) . This is from an older PWA 2.x version. Please do not try to mix code from older version. Use only the coding provided in PWA 3.0.5. PWA 3.0.5 is for 2.3.4.1 FROZEN BS which includes the hook call in application_top.php at the very end: $OSCOM_Hooks->register(basename($PHP_SELF, '.php')); Only if you do not have this in application_top.php you need to add to checkout_process.php: $OSCOM_Hooks->call('checkout_process', 'PwaCheckoutMailMod'); Observe that the "echo" you have in front is totally wrong. Point 2: Redo your installation like explained before. Make sure that you have the Header Tag module and the checkout_success content module correct installed.
  3. 1 point
    They are admin/includes/classes/payment_module_info.php (class paymentModuleInfo) and includes/apps/paypal/cfg_params/transactions_order_status_id.php (class OSCOM_PayPal_Cfg_transactions_order_status_id). Neither class seems to be invoked, so no harm done (yet). I don't know if it's better to add a dummy __construct(), or change the constructor name of these two.
  4. 1 point
    It's the standard MySQL % searching. One of the next updates will move the searching to an Elasticsearch server.
  5. 1 point
    burt

    Frozen bug list

    Could someone please help and go back through this thread dragging out all the bugs (only the bugs) and repost them in one post. Thank You.
×