Ads stacking on top of each other and going off page

ventadmin

HI I recently have ads stacking on top of themselves about 6 currently both desktop and mobile (probably tablet too), in a list at the base of my pages and going off screen. I have put the list in a div and filtered the div id with the css filter and I have also added li and ul to the css filter to stop ads being placed in these. I have tried removing some of the auto ad placeholder numbers but it only lets you remove 2 of 3 devices, seems deleting not possible and even blocking from some devices it just places different numbered ones in the same place. It looks a real mess. Do I just turn off the all auto placements somehow? The original placements were done by the relationship manager that invited me to ezoic last year. Thanks

Lilla

ventadmin Could you please send a screenshot of what you're seeing? I've been testing this and so far, have been unable to recreate anything.

ventadmin

Hello Lilla, It seemed to be fixed but then after a few refreshes it chose those placements again:

Coley

ventadmin Hi there! I tried refreshing a few times but was also unable to replicate this. Is this happening on specific URLs for you or does it seem to happen anywhere on the site? If there are any particular URLs can you let us know so we can make sure to check there? When this issue occurs, what browser and device are you using? Any further details you can provide will help us more effectively troubleshoot this issue. Thanks!

ventadmin

Coley Hello, It seems to be happening on the 'low' definitions layout only so if try e.g com/80-over-50/ and then click any other links in that problematic list at the bottom of the page they all have the issue. Happens on Chrome, Firefox, Edge, Chrome Android basically everything I've tried it on. Thank you

Tucker_P_Ezoic

I'm able to recreate this at the bottom of the articles --- give me a few minutes I'll try to clean things up a bit for us 🙂

Tucker_P_Ezoic

Just so you're able to see how to troubleshoot this --- using the Chrome extension and activating the placeholders, you can identify which one's are causing the issues.
I'm going to disable a few of these on the /80-over-50/ URL just to see if we can't get that page working right to start.

Is this occurring on more than a handful of pages?
If it's occurring in quite a few places, we might be better off having you disable wp-plugin placeholders for 'incontent_24' on down (so 25, 26, 27 etc.)

Tucker_P_Ezoic

Alternatively, rather than trying to stop these on every page or even in bulk on the /80-over-50/ URL, you might want to setup an exclusion filter for the wp-plugin placeholders just for the area of the page where those links usually sit --- since that appears to be the problem area (Similar blood pressure readings🙂.

ventadmin

Thank you. Although I had set css filters on the pubdash.ezoic.com/ezoicads/adpositions/adtypes/autoinsert page it's the first time I found a similar settings page existed in the plugin. I tried adding the div's id into a new filter as #similar_readings with or without the hashtag and also tried completing all three lines but every time I saved it it said 'bad filter'. I saw the identify content setting at the top of the page had both 'p' and 'li' tags and while I had already excluded li in the css filter on pubdash, once I removed it from this plugin setting and saved it, the problem was solved on all affected pages. Perhaps the plugin settings take precedent over the pubdash settings.

Thanks for your help.

ventadmin

Hello ever since I changed the filter setting to exclude list elements in the plugin and saved it I have not been able to re enter the Ad Settings area in the plugin. It has been on the 'placeholders are still being generated' notice for month now. Clicking the 'lets go' button does nothing, nor does deactivating and reactivating the plugin to change this. When I check the console there are the same errors produced as follows:

< screenshot-2023-10-12-171002.png >

Ethan

ventadmin I've regenerated those ads on the backend, clear the cache and this should be resolved, but let us know if not.