yaniv14

yes its safe. its just basic tb htaccess configurations.

I can't tell what those cookies for. check the domain related to those cookies. basically you shouldn't have any problem with cookies from you tb shop.

Not really, but you can keep it on until everything works fine.

it looks like you have bad redirect from http to https. you need to make sure you remove https (just for now), also in seo & url remove the ssl part. https://newshop.alwayspaws.com/contact-us - this one loads. and it still redirect to https. so maybe you have redirect from you dns settings.

yes

Can you turn off https from back office

try to rename .htaccess file to .htaccess.old and regenerate again from back office. and paste the new content again.

Do you see your images now?

it should be fine within admin. are you using any caching or module for cache or anything?

can you remove all these lines: RewriteRule .*.(jpg|jpeg|gif|png|bmp|png)$ - [F,NC] RewriteCond %{HTTPREFERER} !^$ RewriteCond %{HTTPREFERER} !^http://alwayspaws.com/.$ [NC] RewriteCond %{HTTPREFERER} !^http://alwayspaws.com$ [NC] RewriteCond %{HTTPREFERER} !^http://newdev.alwayspaws.com/.$ [NC] RewriteCond %{HTTPREFERER} !^http://newdev.alwayspaws.com$ [NC] RewriteCond %{HTTPREFERER} !^http://thirtybees.alwayspaws.com/.$ [NC] RewriteCond %{HTTPREFERER} !^http://thirtybees.alwayspaws.com$ [NC] RewriteCond %{HTTPREFERER} !^http://www.alwayspaws.com/.$ [NC] RewriteCond %{HTTPREFERER} !^http://www.alwayspaws.com$ [NC] RewriteCond %{HTTPREFERER} !^http://www.newdev.alwayspaws.com/.$ [NC] RewriteCond %{HTTPREFERER} !^http://www.newdev.alwayspaws.com$ [NC] RewriteCond %{HTTPREFERER} !^http://www.thirtybees.alwayspaws.com/.$ [NC] RewriteCond %{HTTPREFERER} !^http://www.thirtybees.alwayspaws.com$ [NC] RewriteCond %{HTTPREFERER} !^https://alwayspaws.com/.$ [NC] RewriteCond %{HTTPREFERER} !^https://alwayspaws.com$ [NC] RewriteCond %{HTTPREFERER} !^https://newdev.alwayspaws.com/.$ [NC] RewriteCond %{HTTPREFERER} !^https://newdev.alwayspaws.com$ [NC] RewriteCond %{HTTPREFERER} !^https://thirtybees.alwayspaws.com/.$ [NC] RewriteCond %{HTTPREFERER} !^https://thirtybees.alwayspaws.com$ [NC] RewriteCond %{HTTPREFERER} !^https://www.alwayspaws.com/.$ [NC] RewriteCond %{HTTPREFERER} !^https://www.alwayspaws.com$ [NC] RewriteCond %{HTTPREFERER} !^https://www.newdev.alwayspaws.com/.$ [NC] RewriteCond %{HTTPREFERER} !^https://www.newdev.alwayspaws.com$ [NC] RewriteCond %{HTTPREFERER} !^https://www.thirtybees.alwayspaws.com/.$ [NC] RewriteCond %{HTTP_REFERER} !^https://www.thirtybees.alwayspaws.com$ [NC] RewriteRule .*.(jpg|jpeg|gif|png|bmp)$ - [F,NC]

And disable friendly url. also can you paste the content of your .htaccess file

Can you turn debug on?

Files & Folder permissions are related to your server. You can do it with FTP client or via cPanel (if you have). You need to make sure that your files are readable by the web server, so you need to make sure they have 644. Folders should have 755 permission. If you are using VPS and have access from command line, you can run. sudo find your-folder -type f -exec chmod 664 {} + and sudo find your-folder -type d -exec chmod 775 {} +

Check your folder and files permission

Preference -> Seo & URL -> turn on or off friendly urls and save.

try to regenerate the .htaccess and see if you get any luck.

I think this forum chat use https://github.com/NodeBB/NodeBB

@mdekker I can confirm that on a store migrated from PS, the duplicate url tab in BO is missing. This is the issue started this discussion.

@alwayspaws This should go in .htaccess under adminxxxx folder. If you don't have that file than create a new file.

I haven't tested this yet, but maybe you should take a look at the new section "duplicate urls" under preferences. About being penalized, why do you think you will be penalized? The idea is to get a new name to one of those categories, like: korg-1 or something.

Can you decrypt the error message? Adv params -> logs

Did you set it up as: AdminDuplicateUrls

Can you try to disable mod_pagespeed in htaccess? ModPagespeed off

Can you check the image url with chrome inspect element

Yes its possible but most likely you will have to override admin controllers.