gaszer

@jageo Thanks for that last bit. Just wanted to thank you for the input on the .htaccess file.

You save me banging my head around. And Telus hosting is really something of a joke. And the phpMyAdmin had me scratching my head as well… :0)

@jageo How did you finally resolve this?

I’m faced with the same issue (crappy Telus hosting support… lol). I see your site is working now.

What came to my mind was doing a fresh WP install into the secure folder, migrating the DB (with the paths rewritten),Then copying the WP files into the new secure folder.

If that works out I would only need to do a redirect from the public folder to the secure folder? If I’m going about this the right way?

I was going to use the Really Simple SSL plug as well as it has served well on other sites (with better hosting)

Just to add to this thread, as the above methods weren’t working for me on the Siteground installation. The following video tutorial was suggested by Siteground support, and it worked flawlessly. It involves adding the auto_prepend_file variable through cPanel.

• This reply was modified 6 years, 10 months ago by gaszer.

Excellent – that plugin worked seamlessly!

Thanks Fabio!

I’ll check that plugin out as well. I tried this one as well yesterday:
https://www.ads-software.com/plugins/easy-google-fonts/ with success (although it would be nice have the font displaying while building slides).

Crelly is an excellent slider by the way! Great work!

Thanks Bet.

I have resolved the problem, and for reference here is what caused it.

I had moved the site (which was not a multisite) from a GoDaddy managed WordPress plan onto just a shared hosting server. I followed best practices when migrating the site, but failed to notice that GoDaddy had files in wp-content in a folder named mu-plugins. After deleting that folder, everything returned to normal when creating a new site and all the links began to work.

And yes, I was attempting to save the settings in the network admin edit sites dash.

Thanks! Worked like a charm!

I had actually tried that before you responded, but had forgotten the # tag before the color. ;0p

Thanks again!

Great slider! Love the element transitions and animation!

I just tried the above CSS to add a shadow below the slider, and it works great. My question is, that I see the box shadows between slide transitions, and it doesn’t look great. Is there a solution to that?

Just that the shadows add a bit more dpeth to the slider.

thanks!

I’m giving a thumbs up to Roy as well!

Could not get the add to cart button to show, and had suspected server settings or JQuery. I would like to have this working without the plugin (but a great thing!) so, it would be nice to have an explanation as far as what the fail points are and how to rectify them on a shared hosting account.

As well, t would be nice to have a further explanation from Woo as far as what to watch out for from server side issues.

From what I have been watching over the past bit, this is not an uncommon problem.

Anyway… Thanks Roy! You are a lifesaver!

Nobody was answering you/ I know that feeling.

I’ve been struggling with the same problem for over a week, with no responses from Woo support. It looks like it actually might be a server side issue.

Today I came across this from Roy Ho (and thumbs up to him!):

https://splashingpixels.com/woocommerce-jquery-cookie-js-error/#comment-152

Let me know if that works for you as well, because I have a few sites to fix up.

Thanks Ovidiu. That worked for me as well. Just wanted to mention that the line to edit is in the swfobject.php file.

I haven’t a clue where it might be – I have 149 posts, but I’m assuming by the line number that it’s probably near the top.
Since I posted, I did fix one of the blogs, but the error page did point me at the right post. Are we restricted to UTF-8 encoding for the RSS feed, as it does seem to be invalid characters in the posts themselves causing the problem…

Okay, got it working. It looks like the .htaccess file I created locally and then uploaded was corrupt in some way (it seemed to have the right permissions), but as soon as I made a blank .htaccess file, uploaded it, and then edited it with WordPress, it works fine!

No, there are two separate installs in two different directories…..

Gracias!