Menu Content

Support

> Forums, FAQs & Paid Support
Welcome, Guest
Username Password: Remember me

Magento M-Turbo Full: getstatichtml.sh
(1 viewing) (1) Guest
Magento E-Commerce accelerator component.

TOPIC: Magento M-Turbo Full: getstatichtml.sh

Re: Magento M-Turbo Full: getstatichtml.sh 8 years, 3 months ago #23928

  • jich
  • OFFLINE
  • Posts: 254
I think that './' is relative path. It needs to enter you absolute path. For example (/var/www/public_html/magento/).
ARTIO Support Team
The topic has been locked.

Re: Magento M-Turbo Full: getstatichtml.sh 8 years, 3 months ago #23929

My server is windows server 2003. The absolute path isn't work. It works fine when set to ./. It's the relative path of webroot (www.domainname.com)
The topic has been locked.

Re: Magento M-Turbo Full: getstatichtml.sh 8 years, 1 month ago #25003

I have the same "too small or 404 error" message on clearly existing frontpage.

All seems to be setup just fine though. Any pointers where to look?

In addition to the above:
I am testing a multistore, on another domain than the admin.

These are our base dir settings, i assume these are right, or do they need a special prefix like magento config does with multistores?
/usr/www/virtual/in2/www.ADMINSITE.com/mage15


Tested site is here:
/usr/www/virtual/in2/www.MULTISTORESITE.com/


Please advise.
Last Edit: 8 years, 1 month ago by inveritas.
The topic has been locked.

Re: Magento M-Turbo Full: getstatichtml.sh 8 years, 1 month ago #25049

  • jich
  • OFFLINE
  • Posts: 254
Hello,

> I have the same "too small or 404 error" message on clearly existing frontpage.

This message appears when M-Turbo incorrectly downloads a page or the downloaded page has the same title as your CMS page 'no-route'. We recommend look at download test on the "Main Configuration" tab in the M-Turbo admin panel. If test fails try to change download method. Else try to check title of your 'no-route', please.

> These are our base dir settings, i assume these are right, or do they need a special prefix like magento config > does with multistores?

M-Turbo builds url by your configuration. There must be only rightly set "Server Name" and "Base Dir" for your website on the "Website Configuration" tab. This settings does automatically, but it is good to check it.

Thank you for your interest. If you will need to help, let us know.


jich
ARTIO Support Team
The topic has been locked.

Re: Magento M-Turbo Full: getstatichtml.sh 8 years, 1 month ago #25051

Hi, we did all tests, all go well.

I noticed the only store that had a cache page made is the first one in the list, top one on the websites tab. It is stored in the var/... directory, htaccess does not yet take care of actually using the page.

The other stores have the same setup and details (server, path).

When i try to make the htaccess for all stores/pages the admin url goes error 500.

I assume this htaccess in the main Magento admin directory will eventually hold all rewrite conditions for the multistores, right? Or do the htaccess files in each individual url have to be edited?


Sidenote: We lost LOTS OF potential clients past 8 hours due to sudden 503 errors in the main two stores we own:-/ -> FIXED BY CLEARING CACHE.
Last Edit: 8 years, 1 month ago by inveritas.
The topic has been locked.

Re: Magento M-Turbo Full: getstatichtml.sh 8 years, 1 month ago #25097

I'll reply to myself then ...

We have more than one URL per website (each storename is a seperate website), this does not work on our end and made our website unreachable for a while these past days.

I am not saying this script is the cause, but it is the only thing we're working with now.

I had hoped this would work out of the box, unfortunately it does not. The lack of support here doesn't help.

No tutorial on multistores under Websites. Only per website.

Another question before we'd like a refund:
Servername is added (not in screenshots, are in admin area), when we enter the name of the server, it is different from what is default filled in there (which we only saw after we UNinstalled, after which it installed itself again?!?). What was filled in was the URL (no www), is this what you use as servername, or does it need th eREAL servername what we filled in?

Either way, we've been trying for days to get it to work on our stores, we ended up with broken stores for two days:-(
Either our fault or well, not ...


Any chance of an explanation to multistores, or do we have to call it quits?
The topic has been locked.
Moderators: pedu
User Login Empty