lesley

Hey, you might be able to fix this one, ftp into the module and replace the contents of the paypal.php file in the module with this, (removed wrong link) Last minute commit had some hidden characters in it.

Can you pm me access? Or do you want me to explain how to roll back the module?

I have just pushed live a release for the Paypal module that fixes the "An error occurred" message. I also released an updated version of the Bees Blog, with several new SEO focused features, bug fixes, and some new hooks for the module. Both releases should be live in your back offices.

The updated module has been released, it should be in your module feed in your back office now. It has the fix I sent over today.

Its because that the module generates cache files for all different crossing selling options, basically one set of options per product. 500mb of space for a cache is not a lot.

I am actually considering how to move it all to the forum, that way we can better manage it and lose the wordpress integration.

It will be possible at some point in the future. It is a good feature we need to have, something we just have not been able to add in yet.

Turn debug mode off in the back office. Or debug profiling.

Ahh yeah, that is a nice a module. I have not tested it too much, but the core was actually something someone at prestashop developed, and never finished.

Great, glad it is working. I am not sure what you mean about the in-context editing.

I think you should be able to set them as approved now. I made you a proofreader on the translations. LEt me know if that does not work.

You can PM me your crowdin username or email and I can approve it.

What payment gateways are you using @Pedalman ?

I will set up an account with them today and test. We have seen several problems coming from their service.

What plan do you have with them? I think the best thing to do is for one of us to sign up to an account and test with them.

Tell me about your hosting, I have seen issues with ipage in the past with thirty bees. Do you know what version of php you are running on the server?

Yeah, there will be one soon. I am familiar with the issues, that is why I have been testing a fix out to make sure it will work for the widest group of shops.

Great, I think this has been tested well enough, I just committed it, we will release a build soon that includes it.

I think it will be problematic to track the whole software. If I were going to track the whole software, I would track a dev site. Then I would get everything right on the dev site, with merged commits, tested packages, ect. Then I would pull the live site from the dev site. That is the only way I can see it happening since you will be editing core files, modules, and other files.

Are you wanting to track the whole software, or just the theme?

In the paypal module, replace the classes/PayPalRestAPI.php file with this file and see if it works, https://gist.github.com/Dh42/09eb812b0c5d7f8d7cfdc1a8e3c28c98

I guess that solves that.

Seems to work rather nicely. There are a couple things we might want to tweak depending on community input 1. It looks like the module is hard coded to use ssl. So we need to either add something to the htaccess to allow cross origin from non ssl to ssl to people, or just detect and use what is currently being used. On the first try it got blocked because of a cross origin request to the domain I was using, but I was logged into the back office with the non ssl url. 2. I think there should be an option to exclude the theme. 3. I think we need to have something in place to set aside the stats modules. Like if someone goes from 1.0.3 to 1.0.7, the shop will just not work because the old stats modules are there.

Shipping costs can only be figured in a real narrow set of circumstances without an address.

It looks like not all of the files upload, specifically the vendor/swiftmailer directory. I would re-upload the files again.