Last post 10 min ago

Posts last week 94

Average response time last week 34 min

All time posts 67889

All time tickets 10493

All time avg. posts per day 20

Helpdesk is open from Monday through Friday CET

Please create an (free) account to post any question in the support area.

Please check the development versions area. Look at the changelog, maybe your specific problem has been resolved already!

All tickets are private and they cannot be viewed by anyone. We have made public only a few tickets that we found helpful, after removing private information from them.

#1470 – Article Save not working

Posted in ‘sh404SEF’

This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Tuesday, 01 December 2015 04:22 UTC

peterrosenfeldt

Hi there
I am not sure even if this is related to sh404SEF but I suspect it is.
These two websites are identical, they have the same root folder.
xxxx.com
xxxx.com.au
To reproduce the issue go to the footer and login to the front end as username xxxx password xxxx
now go to xxxx.com.au/prices and try and save the article. Nothing happens and Firebug reports the following error:
TypeError: document.formvalidator is undefined
{if(task=='article.cancel'||document.formvalidator.isValid(document.getElementBy...

Now replace the domain xxxx.com.au with xxxx.com and repeat the steps. Now the article saves no problem. What can be the issue here ?

Regards
Peter

Tuesday, 01 December 2015 08:47 UTC

wb_weeblr

Hi

I don't see how sh404SEF could be involved in that. What I see however is that you're loading the Joomla validate script through page speed, and having the same content on 2 domains could cause an issue there?
[xxxx]

I just checked out a few pages on both sites, and that's not the only place where things are breaking I think. On the about us page, the facebook buttons have a JS error, on the calendar page, there's no error, but the rendering is not the same, the "Jump to month" button is showing on one, not the other,..

Why would you have the site accessible from 2 domains? it's really, really bad from an SEO standpoint, at least you should pick one and have canonical tags on the other?

Rgds

Tuesday, 01 December 2015 21:46 UTC

peterrosenfeldt

Hi there

Thank you for your reply. I don't want it to be accessible from two domains, I just did that to trouble shoot it. I wasn't using xxxx.com so I just pointed the domain at the same folder on the server. Weird that it works from that and not the main one. I have reverted that because you're right I don't want to risk messing up the SEO which is excellent on the site. They are both add-on domains to my main account which is xxxx.net which is offline so Google doesn't index it. The website can be accessed however from the fully qualified path to it's folder http://www.xxxx.net/xxxx.com.au
and accessing it like that the Save also works. Very weird all round.
Regards
Peter

Wednesday, 02 December 2015 09:11 UTC

wb_weeblr

Hi

That's still a fairly weird setup though, the site should not be accessible from the folder either.

Anyway, I can't really see why this is not working. Like I said, the only option I can think of is pagespeed being confused by the multiple domains, but even that is a bit farfetched.

Rgds

Wednesday, 02 December 2015 23:34 UTC

peterrosenfeldt

Hi there
That's how the GrowBig accounts at SiteGround work. You have the account domain which in my case is xxxx.net then in cPanel you create an Add-On domain with a document root relative to the main domain's home folder (see attached). You then set the DNS of the Add-on domain to be the same as the main domain and traffic to the sub-domain is automatically routed there. But of course you can also get to the add-on domain site by going to xxxx.net/addondomainrootfolder.
I'm surprised you didn't know that.
Regards
Peter

Thursday, 03 December 2015 01:55 UTC

peterrosenfeldt

Hi there

Another weird thing has started to show up. If you go to xxxx.com.au and click on Calendar it tries to go to http://www.xxxx.com.au/xxxx.com.au/calendar which doesn't exist. You click again and it goes to the correct address at http://www.xxxx.com.au/calendar
This just started happening and I have no idea why, it also happens on some of the other pages. Please feel free to login to the backend using xxxx
Regards
Peter

Thursday, 03 December 2015 01:57 UTC

peterrosenfeldt

I think it may just be a browser caching issue because on my phone all the menu items work fine

Thursday, 03 December 2015 13:40 UTC

wb_weeblr

But of course you can also get to the add-on domain site by going to xxxx.net/addondomainrootfolder.

I'm surprised you didn't know that.

Regards

I was not saying it was not possible. I was (am) saying this is fairly bad and risky as you never know if a search engines won't pickup a link somewhere and start crawling it.

This has nothing to do with hosting, what you describe is standard practice and has been so for many years.

What's not good is letting this happen. You should have .htaccess rules (on your main site) to block rendering when request is not coming thru http://www.xxxx.com.au, and disallow any access thru http://www.xxxx.net/xxxx.com.au

I also don't see any problem with the Calendar URL ATM.

Rgds

Thursday, 03 December 2015 22:00 UTC

peterrosenfeldt

Hi there
That is very good advice thank you I will do so.
On the original issue I have managed to solve it. Pagespeed must have been broken because after diabling it in cPanel on xxxx.com.au and re-enabling it I can now save an article on the front end.
Thanks again
Regards
Peter

Thursday, 03 December 2015 22:28 UTC

peterrosenfeldt

Further to the above xxxx.net is always offline so I am am assuming that would prevent search engines indexing sub-directories ? I also have Disallow in the robots.txt on the directories for the add-on website so that allows me to access the sites via the main domain if necessary but not risk messing with the SEO.

Friday, 04 December 2015 09:14 UTC

wb_weeblr

Further to the above xxxx.net is always offline so I am am assuming that would prevent search engines indexing sub-directories

Not if they can access it. The offline mode is just for the site xxxx.ne itself.
If you can view http://www.xxxx.net/xxxx.com.au and it renders, then search engines can see it as well.
What they miss to index it is a link to get started with. They won't find that subdirectory by themselves, unless somewhere on the web lies a link to it. If they pick it up, then they will someday explore that link and index it.
It may then compete in results with your own site.

Same for xxxx.

Rgds

Saturday, 19 December 2015 05:34 UTC

system

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.