Jump to content

nurelm

Members
  • Posts

    20
  • Joined

  • Last visited

Contact Methods

Profile Information

  • Location
    Pittsburgh, PA
  • Activity
    Web development agency

Recent Profile Visitors

2,631,157 profile views

nurelm's Achievements

Newbie

Newbie (1/14)

2

Reputation

  1. Hi @eric.arnoldy, it looks like there might have been a problem installing the module. We see this happen sometimes with PS module installs, where somehow the install gets botched through no fault of your own. Please try uninstalling the AvaTax module, then for good measure removing the [prestashop]/modules/avalaratax/ directory completely. Then reinstall and see if the same file is reported as missing.
  2. Hi Sam, We haven't seen this issue before, and have sent you a note via our support system asking for a few details on the tax code you entered. Hopefully we can find the solution and post an answer here for anyone else who may be encountering the same problem. Thanks
  3. Hi Iyalla, we have heard from a number of users that the Leo Themes conflicts with the Avalara module (along with a few other modules). Please contact Leo's support to see if they can offer suggestions on how to avoid the conflict. Thanks and sorry I couldn't offer more help on that issue!
  4. For anyone arriving at this topic, here's a summary: If you are running PrestaShop on a version of PHP that is older than 5.5.x and using version 3.5.6 of the Avalara module, you'll either need to update PHP to 5.5.x or following this procedure: https://github.com/nurelm/prestashop-avalaratax/wiki/Issues-with-PHP-5.4.x-and-Module-Version-3.5.6 Also, be sure to check out the README once you update to make sure your Avatax module setup is correct: https://github.com/nurelm/prestashop-avalaratax/tree/v3.5.7 And, please make sure you backup your store before making ANY updates, and preferably make all updates on a staging server prior to doing so on a live server Good luck!
  5. It looks like you may be using a version of PHP that is older than 5.5.x. If that's the case, you'll either need to update PHP to 5.5.x or following this procedure: https://github.com/nurelm/prestashop-avalaratax/wiki/Issues-with-PHP-5.4.x-and-Module-Version-3.5.6 Also, be sure to check out the README once you update to make sure your Avatax module setup is correct: https://github.com/nurelm/prestashop-avalaratax/tree/v3.5.7 And, please make sure you backup your store before making ANY updates, and preferably make all updates on a staging server prior to doing so on a live server Good luck!
  6. It looks like a lot of things might be going on here at the same time. Initially when you updated 4 modules, you saw an error with the Avalara module due to an old version of PHP, but updating PHP seems to have caused another problem resulting in a 500 error. Debug mode didn't provide an error, and a good next step might have been to look at the server logs for the root error. But, you took an alternate logical step of rolling back PHP, and now it seems that you're seeing a problem with the eBay module. My suggestion at this point is to roll the store back to a known good backup, and try making these updates on a development or staging server, where your main site will be safe, rather than continuing to work on the live site. If you can restore your main site to a good backup, we can help you work through the situation on a staging machine. For anyone arriving at this topic with the same issue, here's a summary: If you are running PrestaShop on a version of PHP that is older than 5.5.x and using version 3.5.6 of the Avalara module, you'll either need to update PHP to 5.5.x or following this procedure: https://github.com/nurelm/prestashop-avalaratax/wiki/Issues-with-PHP-5.4.x-and-Module-Version-3.5.6 Also, be sure to check out the README once you update to make sure your Avatax module setup is correct: https://github.com/nurelm/prestashop-avalaratax/tree/v3.5.7 And, please make sure you backup your store before making ANY updates, and make all updates on a staging server prior to doing so on a live server. Good luck!
  7. Kevin, can you turn on debug mode and report back if it alerts you to any errors? (http://www.psfever.com/blog/2014/how-to-enable-debug-mode-prestashop-1-6/)
  8. Hi Kevin, you will see that issue if you are using a version of PHP that's less than 5.5.x. We have created an update to solve this, and are currently awaiting PrestaShop to review and release it. Meanwhile, the resolution is fairly simple. You will either need to update your version of PHP to 5.5.x, or replace one file. This process is explained here: https://github.com/nurelm/prestashop-avalaratax/wiki/Issues-with-PHP-5.4.x-and-Module-Version-3.5.6 Also, be sure to check out the README once you update to make sure your Avatax module setup is correct: https://github.com/nurelm/prestashop-avalaratax/tree/v3.5.7 Let us know how it goes, and good luck!
  9. Copernican Theory: Awesome. Just head to nurelm.com and shoot us a note if you have any issues down the road with the module.
  10. Copernican Theory: Awesome, I'm glad that worked. I would [cautiously] remove that 2nd folder with the long name, start by just moving it out of your prestashop folder and test everything prior to deleting it. lweinlan: I'm sorry to hear of the bad experience you had a month ago. We actually started work on the module prior to that, and were working with Avalara support to communicate updates through them while we focused on making updates to the module. We've been communicating through our support email since this morning, and will continue working with you until any issues you're having are resolved to your satisfaction.
  11. Hi Everyone, We've recently taken over maintenance of the module, and have made a ton of updates to the module that should make it a much more useful tool. We're sorry about this issue. It's due to changes between the version of PHP you're using vs the PHP version modules are tested on. It looks like you're using a version of PHP that's lower than 5.5.0, which handles a function that the module uses slightly differently. There are 2 options to resolve this: Option A ) You can update to PHP 5.5.0, or Option B ) If updating PHP is problematic, you need to make 2 changes to one file. The file is modules/avalaratax/avalaratax.php, here are the two lines to change: Change #1: If you're comfortable with Github, this is the change to make. Or, go to line 589, which should look like this prior to updating: if (empty($s_cart['cart_id']) || empty($s_cart['customer_id']) || empty('customer_tax_address_id') || empty('carrier')) { and change it to this: if (empty($s_cart['cart_id']) || empty($s_cart['customer_id']) || empty($s_cart['customer_tax_address_id']) || empty($s_cart['carrier'])) { Change #2: Either use this Github commit listing, or Go to line 1638, which should look like this prior to your update: if (!empty(trim($entity_use_code))) { And change it to the following: if (!(trim($entity_use_code) == false)) { Please let us know if that does the trick, and we'll report back if we find any further PHP version issues. Meanwhile, we'll test on older versions of PHP and push all the updates once that's done.
  12. I am having the same issue. error for copying /CONTRIBUTORS.md error when trying to upgrade /CONTRIBUTORS.md [ERROR] file V1.5.3.1_20130805-154946-7b528d8d is missing : unable to restore files. Operation aborted.
  13. One final note to confirm that this issue is resolved. We uninstalled both the UPS and FedEx modules that come with PS. Both turned out to be extremely slow. We installed Prestochango's modules, and adding an item to the cart is now reasonably fast (2.5s for the AJAX call before it is cached ... would like it to be faster, but this is at least acceptable ... and a fraction of a second once the shipping rate is cached). Thanks to mikey3232 for pointing us in the right.
  14. It turns out that mikey3232 was right on the money. We tried disabling both FedEx and UPS with no effect, and decided that wasn't the issue, but when we finally just completely uninstalled both it worked. Turns out that FedEx is causing our problem (using just UPS works). Does anyone know if that module makes a request when adding or removing a product to a cart that might be getting blocked? Meanwhile, we'll try installing Prestochango's FedEx module to see if it works properly.
  15. One more note: Switching to the default theme does not seem to resolve the issue, either.
×
×
  • Create New...