legendarymage

I think I might have figured out finally what the problem could be. This current account that I’m using to connect is added as an administrator to my original ‘personal’ gmail account (where AdSense was originally created) and is therefore not the first one.

Do you think this could be the problem? I’m going to try and log into my first account later today (have some 2F issue at the moment) and when I try to connect AdSense this time I’m going to instead select that one. I’m almost entirely sure that ‘could’ be it. If it is, I’m sorry for wasting your time!

I only have that one, if I remove that one there won’t be any left. I removed the manual unit, right now there’s only the plugin’s code and it’s still the same.

Which information are you most interested in? I’m not 100% comfortable sharing everything that’s there publicly. Thanks.

I have a manual placement in one place on my site, but this didn’t seem to be a problem before as I mentioned (including the ‘third’ instance of manually placed auto-ads). Do I really need to get rid of the manual unit to get this to work again?

Settings page: https://ibb.co/GVXDtS6

AdSense page: https://ibb.co/XXtZyF2

Dashboard page: https://ibb.co/YNtHRqg

Cleared my browser cache, site cache, tried 2nd browser, reset the plugin and started from scratch etc. Any particular sequence I should do to make it work?

It’s weird because it used to work shortly ago, and that was WITH the double codes (still had it in ‘header’) but ever since I migrated to SiteGround a few days ago, this issue wouldn’t go away.

Thanks. I still see the error though. Any ideas what might cause it? I tested in another browser as well just to make sure it’s not a cache issue, but still the same (Opera & Chrome). I’m sure it all works – but I’d like to see the data from the module as well.

Can you please check the code now? I removed the manual entry from the header file and just left the plugin to manage it.

Yeah, my bad. I just found the 2nd instance, when I searched for the whole string it only found one, when I just tried ‘page_level’ I could find the 2nd. Sorry again, I’ll give it another go now without the manual one.

Does the auto ads code placed by the plugin include page level ads? There seems to be a difference between the scripts where one is explicitly included (manual) and the other is not. Can you please confirm this?

In the meantime I have tried disabling the placement from the plugin and reset everything but it’s still the same issue. So it seems I might not have a choice if I want to have this capability available.

Edit: Nevermind, I see you said ‘twice’, I’ll check again – might have missed it, sorry.

• This reply was modified 5 years, 2 months ago by legendarymage.

So I compared the two codes and I see that in the one I manually put, page level ads are also included, while the second one doesn’t seem to have that. I would like to keep that capability of course.

So you suggest to just remove site kit’s auto ads placement since I already have that manually added from before? I was under the impression that they would work together out of the box and the plugin would simply detect that such a setting was already applied.

Thanks Donncha, appreciated! I’ll do that too, keep up the good work by the way!

Thank you xrampage16!

Yes, I do have the cache rebuild option enabled but the ‘page is temporarily unavailable’ redirect still happens sometimes (not always), this could mean that the server resources aren’t very good? Weird, I paid quite a bit of money for godaddy’s second tier level shared hosting and there aren’t that many visitors, one would expect it to work flawlessly under those conditions, perhaps I made a mistake there with my host.

The 4th thing happens on more than 50% of pages I’d say, I have a perma link option to use post names as perma links, to make things a little bit more attractive.

Here is my gaming website if you care to take a look, I would really appreciate it. And thank you once again for everything!

https://www.legendarymage.com

Alex

edit: Oh, and I have added the code as you suggested to the appropriate line and it seems that the htaceess prompt is now gone from the ‘advanced’ tab, thank you!

The line looks like this now:

$home_root_lc = str_replace( ‘//’, ‘/’, strtolower( $home_root ) ); $home_path = trailingslashit($home_path);

Maybe it’s not perfect, but it certainly eliminated the message.

• This reply was modified 7 years, 7 months ago by legendarymage.

Right. Well, since I’m not very adept at editing all this code (I checked the line but don’t really know where exactly to ‘add this’ excerpt you mentioned), I did edit the htaccess files the other day and caching seems to work just fine on ‘expert mode’ so I guess I’ll just leave it like that until they patch it for good.

By the way, do you happen to know anything about points 3 & 4 I mentioned above? Mainly the temporary caching redirect, as well as ‘query strings’ at the end of the URLs. This shouldn’t affect something like google in a bad way?

Thank you for your help, it’s greatly appreciated!

Thanks xrampage16! So basically, if I edited htaccess (both of them) manually, then everything works even without adding this, it’s just that the plugin cannot find the htaccess file and reports as if the code is not there?

Oh I see. So problem no1 & no2 is due to this and is expected to be resolved in the next update. Alright.

Yeah, I think I added everything manually and it seems to work for now I guess. Do you happen to know why this ‘temporary unavailable’ stuff keeps popping out every once in awhile? It’s definitely due to the plugin but I’m just worried that it may annoy visitors if it keeps happening and the pages are delayed for a second or two because of it.

Also, this ‘query string’ at the end of posts and pages is confusing me, is that also because of the plugin or just wordpress and is custom url structure (I selected the ‘post name’ as a perma link option to make urls look better).

Thanks a lot Malinc!