Title: Bad Invocation code URL + 3 warnings Last modified: February 18, 2022 --- # Bad Invocation code URL + 3 warnings * [EditionsLVA](https://wordpress.org/support/users/editionslva/) * (@editionslva) * [4 years, 3 months ago](https://wordpress.org/support/topic/bad-invocation-code-url-3-warnings/) * Hi, The js invocation codes add www/delivery/ to the URL src then it gives a 404 : ex. //servedby.revive-adserver.net/www/delivery/asyncjs.php instaed of // servedby.revive-adserver.net/asyncjs.php * Also 3 PHP warnings in the settings form fields : page=wp-revive.php Field Revive Adserver Async URL:
Warning: Trying to access array offset on value of type bool in …./httpdocs/wp-content/plugins/wp-revive-adserver/inc/panels/ wprevive-general-panel.php on line 14
* Field Revive Adserver ID: *
Warning: Trying to access array offset on value of type bool in …/httpdocs/wp-content/plugins/wp-revive-adserver/inc/panels/wprevive-general- panel.php on line 19
* page=wprevive_vast_convert * Warning: Trying to access array offset on value of type bool in …/httpdocs/wp- content/plugins/wp-revive-adserver/inc/panels/wprevive-vast-convert-panel.php on line 25 * PS : you should specify toput //servedby.revive-adserver.net in Field Revive Adserver Async URL when using hosted edition (not easyto find this information in the doc) * Thank you Viewing 4 replies - 1 through 4 (of 4 total) * Plugin Author [SteveSoehl](https://wordpress.org/support/users/zoan/) * (@zoan) * [4 years, 3 months ago](https://wordpress.org/support/topic/bad-invocation-code-url-3-warnings/#post-15400870) * Hello – the hosted edition does not alert its users to the address of their ad server? * Thread Starter [EditionsLVA](https://wordpress.org/support/users/editionslva/) * (@editionslva) * [4 years, 3 months ago](https://wordpress.org/support/topic/bad-invocation-code-url-3-warnings/#post-15401787) * Perhaps but I didn’t find it, i guessed it reading the invocation code . The most important problem to solve is the www/delivery path that you hardcoded in the files : I removed them and it works now but I hope you will remove them or make it a configurable option in the next version. Thank you * Thread Starter [EditionsLVA](https://wordpress.org/support/users/editionslva/) * (@editionslva) * [4 years, 3 months ago](https://wordpress.org/support/topic/bad-invocation-code-url-3-warnings/#post-15404158) * Hello, I add another suggestion concerning GPDR compliance : I think that it would be a good idea to create an option for adding the js invocation code (asyncjs. php) to make it possible to let a GPDR plugin do it instead after authorization. Example of GPDR script [https://tarteaucitron.io/en/](https://tarteaucitron.io/en/) * Thanks * Plugin Author [SteveSoehl](https://wordpress.org/support/users/zoan/) * (@zoan) * [4 years, 2 months ago](https://wordpress.org/support/topic/bad-invocation-code-url-3-warnings/#post-15412685) * The plugin was produced for the self-hosted version. I’ll make changes for the hosted version Viewing 4 replies - 1 through 4 (of 4 total) The topic ‘Bad Invocation code URL + 3 warnings’ is closed to new replies. * ![](https://s.w.org/plugins/geopattern-icon/wp-revive-adserver_6c89a2.svg) * [WP-Revive Adserver](https://wordpress.org/plugins/wp-revive-adserver/) * [Frequently Asked Questions](https://wordpress.org/plugins/wp-revive-adserver/#faq) * [Support Threads](https://wordpress.org/support/plugin/wp-revive-adserver/) * [Active Topics](https://wordpress.org/support/plugin/wp-revive-adserver/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/wp-revive-adserver/unresolved/) * [Reviews](https://wordpress.org/support/plugin/wp-revive-adserver/reviews/) * 4 replies * 2 participants * Last reply from: [SteveSoehl](https://wordpress.org/support/users/zoan/) * Last activity: [4 years, 2 months ago](https://wordpress.org/support/topic/bad-invocation-code-url-3-warnings/#post-15412685) * Status: not resolved