Jump to content
Latest News: (loading..)

yomama360

Members
  • Content count

    96
  • Joined

  • Last visited

3 Followers

Profile Information

Recent Profile Visitors

6,252 profile views
  1. yomama360

    SSL on every page.

    Thanks... In your second example, what would https://www.example.com trigger?
  2. yomama360

    SSL on every page.

    Awesome, thanks again. (I probably could have guessed that, but wanted to be sure). Another ignorant question: you are using {HTTP_HOST}, is there a difference from {HTTPS_HOST} ? If I want to make everything https and non-www I assume my code in the .htaccess should look like this: (and put it before other rewrites) RewriteEngine On # switch all to https RewriteCond %{HTTPS} !on RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L] # Remove www from any URLs that have them: RewriteCond %{HTTPS_HOST} ^www\. RewriteRule ^(.*)$ https://example.com/$1 [R=301,L] Is this correct? Should I remove www first before switching to the https? Would this kill subdomains?
  3. yomama360

    SSL on every page.

    Very awesome thanks. @frankl the linked forum also talked about forcing a redirect to www. Incidentally I want to force a redirect to non-www. How do I do that? Thanks.
  4. yomama360

    SSL on every page.

    I'm a little late in the game on this one. What is the easiest way to make every page switch to https? It switches fine when people go to log in, just wondering if there is a quick, easy way to do it for all pages. Thanks
  5. yomama360

    Upgrading to New PHP - Conflicts?

    Is there an "upgrade to Edge" from 2.3.4(BS) step by step somewhere?
  6. yomama360

    Upgrading to New PHP - Conflicts?

    Thanks. Is there a list or a chart somewhere that will tell me what changes? I dont think it was Edge or Gold. If memory serves, we were live with it Jan or Feb of 2015. So I assume regular 2.3.4. We had to get Burt to do do the bootstrap for us as it was not a package deal yet if I recall correctly. And we did keep track of the mods. But there's a ton of them... uggh, why can't everything just be magic? Thanks
  7. I understand that older versions of PHP will soon be deprecated. How hard will it be to upgrade to a newer PHP? I'm currently running an OSC v2.3.4 (bootstrap) with PHP Version 5.3.29. Heavily modified cart. In early 2015 we upgraded to where we are now from OSC v2.2 (and and older version of PHP) and had tonnes of PHP issues (mysqli for example). Not really looking to do that again. How broken will my cart get if I upgrade the PHP on my server? Is there a "safe" version of PHP I could upgrade too (even if not the latest)? To save time/resources, I intend to leave the OSC cart as 2.3.4 (BS) unless everyone tells me it is imperative I upgrade to something else. Keep in mind I have a lot of mods, and some of them I built (hacked together) myself. My skill level: Not a programmer, but I'm pretty good for a non-programmer. Using OSC since 2005 and have implemented a lot of mods myself. Thanks
  8. yomama360

    Problems with local testing server

    Thanks, I think running the OSc install new (as opposed to just dragging all the files over and modifying) was the key we were missing. Also, for future readers: After install and porting over the old content & database as described above, we were having trouble getting into the admin. Server error! The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there was an error in a CGI script. If you think this is a server error, please contact the webmaster. Error 500 We commented out everything on the admin side .htaccess file and we got in. It might have been some code ported over from the live server. Thanks again.
  9. yomama360

    Problems with local testing server

    Better Question: What are the recommended steps to setting up a testing server for OSc?
  10. We have an existing site working and running OSc 2.3.4 Everything is good, but we wanted to make a testing site for our own in-house mods. We are having trouble getting the local testing server to behave. It keeps trying to jump to the remote live site. When trying to access the admin the browser gives us an error "localhost redirected you too many times. Try clearing your cookies. ERR_TOO_MANY_REDIRECTS" Some things we tried: includes/configure.php files set to point at localhost (do I need to do anything with the includes/local folder? we have nothing in there names "configure.php") the RewriteBase in the .htaccess file changed to point to the localhost Is there something in application_top we need to change? The browser keeps putting an http in front of our localhost Should we have installed a vanilla OSc onto the local server THEN port everything over? As it is, we never installed, just ported over and changed values. Apparently there is something we missed. Thanks in advance.
  11. Strange, so it must be a server setting somewhere. It's the same server, only thing we changed was the PHP version and it worked on PHP 5.3 but not 5.4. As far as I can tell mod_rewrite is enabled. Do you know what other settings need to be on? Thanks -------- @@Tsimi The catalog is in the root of our public_html directory. My RewriteBase path is: RewriteBase / Anything else breaks it. Again, it works file like this if PHP version is 5.3 Arigato gozaimashita -------------- Upon re-reading PHP.net makes the distinction that "call-time pass-by-reference" is deprecated. So apparently a parameter received by reference by a function is still ok.
  12. Is this not in the latest version of seo.class.php? Do a search in seo.class.php for "passed by reference" or "&$" and there are about 8 or 9 references to it. We would love to be able to use PHP 5.4. Is there something else we're doing wrong? Missing a library perhaps? On the same server we run php 5.4, and it only gives the "yourwebsite.com/-p-27.html" URLs. Switching our php to 5.3 makes it work correctly producing "yourwebsite.com/product-name-p-27.html" URLs. The category URLs also do not work on the new PHP. Thanks
  13. Might have something to do with the PHP version. So if the new server is running PHP 5.4 then you will have problems because it looks like quite a few of the functions in the seo.class.php are doing pass-by-reference which is now deprecated. We rolled our Apache server from PHP 5.4 to PHP 5.3 and it works now. We are going to update the seo.class code and see if we can make it work on PHP 5.4
×