Last post 9 hours 6 min ago

Posts last week 81

Average response time last week 4 hours 29 min

All time posts 67934

All time tickets 10501

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.

#1196 – Google Error

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.

Saturday, 24 October 2015 23:57 UTC

boliatepa

On my sites, I get this error:

Error connecting to Google Analytics: Analytics: no analytics web property ID set!

The Google ID is already applied in Analytics> Basic Configuration> Web Property ID

Help.

Chris

Monday, 26 October 2015 10:29 UTC

wb_weeblr

Hi

1 - Have you done the authorization procedure?

2 - Make sure to Clear Joomla cache (under the System > Clear cache menu) for sh404SEF analytics

3 - If you have completed the authorization procedure, then usually the problem comes from using the wrong gmail account for the web property id. Is this possible?

RGds

Monday, 26 October 2015 15:45 UTC

boliatepa

Thanks, that fixed it.

I am seeing this error and it is too vague:

"Joomla settings are probably not correct
Joomla! and sh404SEF SEF URLs settings don't match. This is not required by sh404SEF but some extensions may not work properly. "

Monday, 26 October 2015 15:48 UTC

wb_weeblr

Hi

Well, it says that the Joomla SEF URL settings and the sh404SEF settings are not the same. According to documentation, they should be the same.

This usually means that you have not enabled Joomla SEF URLs, or maybe you enabled to add a suffix to URL in Joomla and not in sh404SEF.

Rgds

Monday, 26 October 2015 15:55 UTC

boliatepa

Again, that fixed it. Great support. Thanks.

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.