Raithlin

Sorry to ressurect an old thread, but it's a year on, and still the same issue. Had no feedback AT ALL from the developers. Any help from the module devs here would be appreciated.

@lekkatime I've been away on business for the last week. No, not yet - but I'm going to do that. I'll revert if I have any feedback.

Okay, I tried cleaning up the URL for redirect - verified this in the log. No joy. Any help appreciated here.

I added the redirect URL to the log. Can anyone confirm if we are missing anything on this? index.php?controller=order-confirmation&key=xxxx24d7a231aa37d91113f6905xxxx&idcart=69&idmodule=100 I see the code is setup as follows: Tools::redirect('index.php?controller=order-confirmation&'.$SERVER['QUERYSTRING']); Is that not perhaps causing the & issues we are seeing on the redirect line above? Would it not be worth recreating the line, as in say the Authorize module? Tools::redirect($url.'idmodule='.(int) $authorizeaim->id.'&idcart='.(int) $cart->id.'&key='.$authorder->securekey);

@lekkatime That's exactly my experience. I have a feeling something may have changed with regard to carrying the order back to the order page, losing it's state.

Putting this in anywhere crashes my site.

Hi all, I'm using ThirtyBees 1.04 with the SagePay PayNow module (3rd party payment gateway) for PrestaShop. Tested with PrestaShop 1.6.11, it works perfectly until it comes back from the payment provider, at which point it simply reverts back to the first order page. The result is a payment without an order. I'm looking at the code to figure out what has changed and why it doesn't get to the order confirmation page. Any help would be appreciated, from where to look for changes to a sample payment module that works - anything that will help me sort this out. I'm a C# developer by trade, but PHP isn't too different, and I've done plenty of web dev over the years. I've taken a look at the code as I said, just looking for some pointers here. TIA

Excellent module! I've used similar modules in the past, and one function that I found useful for my products was a delay. You could specify how long to wait before sending. I don't suppose that's possible with your current implementation, but perhaps something you could consider for future development? Again, thanks!

@slick_303 said in 1.0.4 soon?: oh and delete gridhtml. Thats all the old stats modules, in the new version its consolidated into one module, statsmodule, which you need to install via the BO Thanks. Back office and site working well. Will leave the stats module for now. Got a weird error on install.

Worked perfectly. Thanks mate. For the record, RockPOS still throws errors, even with the new version.

Log shows: PHP Fatal error: Access level to GraphNvD3::$width must be protected (as in class ModuleGraphEngine) or weaker in /home/eclecdhk/publichtml/modules/graphnvd3/graphnvd3.php on line 30 That module isn't in the new codebase. Is it third party or an old one that can be safely removed?

@slick_303 said in 1.0.4 soon?: in the tb_configuration there are a couple version references too Looking for it now.

@slick_303 Renamed the folder *before*. I actually extracted, renamed, removed install, removed .yml, etc. (Vagrant), rezipped and uploaded. I've just found the version in settings.inc.php. Searching for others in case that helps.

@lesley said in 1.0.4 soon?: @Raithlin You can clone your current site, then download the repository and upload the files over your cloned site files. That works for this release since there are no database changes. Done. Can't access my back office though (/backoffice). "Unable to handle this request (Opera)". Shop works fine. Did I miss something? Got a backup, just asking...

@lesley Perhaps I haven't spent enough time in the docs, but I'm not sure how to go about properly testing 1.0.4 without actually upgrading my production site, or creating a new one from scratch. There is no obvious way to go about this - perhaps others feel this way too? #my2c

Has anyone had any issues with mapping on Google Analytics? I use the community default theme (TB v1.0.3) and Google consistently refuses to pick up (or even show, which I think is the problem) product prices. Perhaps it's a cache setting I've enabled somewhere (CCC is disabled), but Opera Turbo does the same thing. I've been asked where my prices are, only to find out that Opera in Turbo mode doesn't render the price.

Is RC2 stable enough for a small ecommerce site?

@mdekker Sounds good. Let's try that.

@pedalman Thanks - already sent them an email, but so far no response. Thought I'd try here.

Hi all. I've been using ThiryBees since 1.01, and the improvements are great. However... I followed the threads here and noted the compatibility would be 100% for now, and installed RockPOS - which I used quite happilty with PS 1.6. Running it on TB 1.0.3 isn't such a pleasure. I get undefined errors on startup, and it refuses to see loyalty points. Is there anyone here representing RockPOS, and if so can we work together to get this resolved? If not, does anyone know where I can start to make the changes myself and then make the suggestion to RockPOS themselves to fix this? I dont want to have to move to another POS if I can get away with it, but business is business...

Works after refresh. Should have thought of that. Thanks @yaniv14 - problem solved! I assume this will be sent out with the next update then?

@yaniv14 said in Product editing issues: grab the latest version of price.js from here. https://raw.githubusercontent.com/thirtybees/thirtybees/1.0.x/js/admin/price.js and replace it with the existing file located at: /js/admin Nope - didn't work. I'll stick with Taxes enabled for now, and just set my products to use no tax. [EDIT] Refresh cache, stoopid. [/EDIT]

To clarify - cross-selling doesn't affect the loading. It's definitely tax that affects it.

@Fathira said in Product editing issues: @ raithlin please jest uninstall cross selling module and say your localization tax setting yes or no ? if no jest try to yes same issue i solved this way Oh my word! That's exactly what causes the issue! As soon as I enable tax, the product loads correctly. Disable tax and the problem re-asserts itself!

I'm having the same issue. Perhaps you can replicate it on my site - I'm busy setting it up from scratch (1.0.2 installed via Scriptaculous, upgraded also to same version to try fix the error), came upon this issue with the first product.