yaniv14

You sql addon looks fine and I believe it should work. Check if you have an override for classes/Product.php in your override folder. and also try to delete "cache/class_index.php" file.

I think the easiest way will be to hook into actionEmailSendBefore and add your attachments. In case your 2 files are the same for all customers than why don't you just put the files on your server and add a link to them in the email body.

The reason I asked about the api key is because on the csv file you attached some of the response where 401 (unauthorized)

I am not familiar with Prestashop 1.7 so I can't tell if its different than 1.6

The people from Parcelforce need to tell you if they are not getting any reply from your web service or they are getting bad/wrong xml format. Are they using the correct Api Key / Token?

Based on your access log it looks that everything is fine on your side and the problem is on Parcelforce side. as you can see your webserver response with 200 (which mean OK) and the numbers you are referring to are the total bytes returned in the response.

The module added a new selection under "Preferences"

You can use the core updater module to upgrade latest fixes that are not build in a new version yet. It called Bleeding edge.

You will need to extend tinymce editor configuration. There is a really old tutorial that might be still similar to what tb have today, but I am not sure because I didn't check it. https://mypresta.eu/en/art/prestashop-16/extended-rich-text-editor.html

Are you using different php version for the new shop? if so, make sure you have all php required extensions installed for the used php version.

I doubt if that error is the cause of the 500 error. can you enable tb debug mode? edit file config/defines.inc.php and change this define('_PS_MODE_DEV_', false); to define('_PS_MODE_DEV_', true); and reload the page and see if you get some other error.

When you change to the new folder/shop, nothing works or you just have an issue with 1 module? I am looking at earlier posts and don't understand the exact error you have. If you want to look for hard coded strings inside files you can use grep command. like: grep -rn "jv74.se/httpdocs" /home/jv74/public_html I am not expert in mysql and I think that if you want to lookup inside your database you will need to dump it first and than run grep. like: mysqldump --compact --skip-extended-insert -u your_db_username -pyour_db_user_password db_name | grep "jv74.se/httpdocs" "-pyour_db_user_password" => the "p" is for password and your real password should be with no space.

But what is the issue now? I am browsing on https://www.jv74.se and I don't see any issues.

Are you sure you are pointing the domain to the correct root folder on the server?

By doing this, you will get your self to the same situation you are right now. Try to download your db and files/folders to your local computer and see if you can get it to run.

What about trying to deactivate the module from phpmyadmin. look for the module name in tb_module and set active to 0.

Did you closed the exec with semi colon?

and if you run. sudo find /home/jv74/public_html/ -type f -exec chmod 664 {} \; sudo find /home/jv74/public_html/ -type d -exec chmod 775 {} \; sudo chown -R apache:apache /home/jv74/public_html/ it still doesnt work?

I think this will give you a clearer picture about user and group. apachectl -S

Try setting file/folder permission. sudo find /home/jv74/public_html/ -type f -exec chmod 664 {} \; sudo find /home/jv74/public_html/ -type d -exec chmod 775 {} \; also make sure you are using the current user, check: ps aux | egrep '(apache|httpd)'

Just change the owner and group to the same one you used in the old path. sudo chown -R user:group /home/jv74/public_html/ user & group should be real user and group

Just make sure you use the same user/group in the new path like you had in /var/www/vhosts/jv74.se/httpdocs

Apache user.

Yes

I think that gift card modules use regular product at the end. So it should direct you to regular product page (with some module customization). Maybe you have another product with the same url rewrite as the gift card product.