lesley

The error before was a template error, does the template error still happen?

Try changing this line https://github.com/thirtybees/paypal/blob/master/controllers/front/pluseu.php#L86 to $this->setTemplate('paypal_plus_payment.tpl');

You would have to delete them in the templates, but yes, it is possible.

@musicmaster This is exactly why we are trying to rewrite the module from scratch. As we have mentioned before we are a small team, anything we can do to save time on tasks is something we have to consider. Since the builds and upgrade builds are so time consuming and this module is so unstable we found this to be a must to do.

Sure, like looking at this sitemap, http://redwrappings.com.au/1en1_sitemap.xml You might need to save it and explode it out something like PHP storm or something. You can see the image files are referenced to the CDN, but the CDN by default has https://cdn.redwrappings.com.au/robots.txt so it is denying the crawling of the images. This is common with some CDNs and an option with others. I was wondering if it would be considered more beneficial to most people if the module just skipped the whole CDN and output the image urls to the source server.

I am looking at how the sitemap module handles media servers and CDNs. What is the general thought of the community? Currently, the module outputs the images to the CDN. Should the module skip the CDN url and output the canonical image address?

Is this using the default theme?

I have been watching this post since it was opened considering how best to respond. I guess I do not understand what kind of progress updates everyone wants. For 1.0.4 we have pretty much finished with it. As @musicmaster mentioned he did a couple of bug fixes in the migrator / updater. They were not included because we are trying to write a more robust solution and not just patch the current solution. This is what the hold up with releasing 1.0.4 is. Our current updater takes around 8 hours to make a version update for. We are trying to do something more streamlined so we can release faster updates, but we need to get the updater fixed first.

The web service will be yes. At some point, we are going to have to start breaking module and theme compatibility though.

Have you modified that file? Or set the permissions differently on that file? You might upload a fresh version from github.

Does anyone know if they actually add sites? Or seen one added before? It seems like over time the list can be billions of lines long and would need to be truncated when sites go out of business.

No worries. They are right. I would disable them all if you are working on the site though.

Right, but the reason for that setting is so that if something caches the front end, like Google or a full page cache, it does not break. Its actually there specifically for the problem you had.

That is the problem. Do not do that.

I do not think the web service API is strong enough right now to handle that. You need a lot of data that cannot come from the webservice. I would embed buttons manually if it were me.

Hmm weird. All that option does is not delete files. Do you delete files from your cache manually?

I would disable all caching opens everywhere, then start turning them back on. Then make sure this setting is always on, https://www.screencast.com/t/Da4GsLZAy and do not manually delete files from your caches.

Are you using the full page cache in your shop?

There is something caching on your server. The pages are not being updated to reflect that those caches are disabled.

Turn these settings to off, https://www.screencast.com/t/wmv6CGrs

Check the error log for any errors on the payment return, that would be the first place I looked.

Actually turn it off for js too. It looks to not be loading files from the themes/your_theme/cache directory

Turn off CCC your style sheet is not loading. Make sure you have a cache directory in your theme.

Likely it was not caused by thirty bees, that is generally an issue with something on the server that causes that error.

Sorry about that.