![]() |
Product | AdPlacer |
![]() |
Preview | View Product Page |
![]() |
Forked from | AdSanity |
![]() |
Original by | Pixel Jar |
![]() |
Version | 1.9.4 |
![]() |
Last updated | 2 May 2025 |
![]() |
Published | 2 May 2025 |
![]() |
Support Policy | Beginner’s guide to using Festinger Vault |
Featured Image
Direct Product Link
Changelog
1.9.4 (Latest Update) - Improvement: Added adsanity_output_the_ad_by_id()
function to allow developers to output ads by ID manually outside of the normal ad placement methods. - Improvement: Added additional filters to the ad list table columns to allow developers to modify the output of the columns. - Fix: Corrected issue where Ads would display to logged-in users when set to only display to logged-out users when using caching plugins. - Fix: Corrected issue where Default Ad wasn’t displaying correctly when an ad was set to display based on a category and no ads matching that category were found. 1.9.3 - Security: Added additional security hardening to prevent XSS vulnerabilities. Thanks to the team at Patchstack for discovering and responsibly disclosing the vulnerability. - Fix: Corrected issue where the ‘Ad Content’ metabox was not displaying correctly in the block editor when editing Ads. 1.9.2 - Feature: Added new ‘ad_group’ URL parameter for tracking Ad Group performance in Google Analytics. Thanks to Simon Fryer for the contribution! - Improvement: Replaced deprecated jQuery usage with vanilla JavaScript in the Ad Health checker. - Improvement: Added additional filters to the ad list table columns to allow developers to modify the output of the columns. - Fix: Corrected issue where ads with start and end dates would sometimes display outside of those dates when using caching plugins. - Fix: Corrected issue where the ‘Ad Content’ metabox was not displaying correctly in the block editor when editing Ads.
Support Rules
To ensure a smooth support experience, please follow these guidelines:
- Check the Documentation First – Reviewing the official guides and FAQs can resolve many common issues.
- Be Clear & Detailed – When asking for support, include details such as error messages, screenshots, and steps to reproduce the issue.
- Respect Our Scope – We assist with installation, basic troubleshooting, and guidance but do not offer custom development.
- No Requests for Original Developer Support – If you need direct assistance from the original developer, please consider purchasing an official license.
Final Words
Congratulations, you made it to the end of this post! Open-source thrives on collaboration, innovation, and accessibility.
At Festinger Vault, we believe in supporting a growing community by providing access to GPL-licensed resources. Whether you’re a developer, designer, or enthusiast, we encourage responsible experimentation, learning, and sharing.
If you enjoy using open-source tools, consider supporting the original developers by purchasing a license when needed. Let’s build together and keep innovation open to everyone.