Aleksandar Uro?evi?

Thank you for choosing Head & Footer Code plugin for your project.

If you have enabled the “Your latest posts” homepage display on Settings > Reading and entered the LINK tag within the “Homepage HEAD Code” under the section “Head, body and footer code on Homepage in Blog Posts mode”, it should be there, like on screenshot below:

https://drive.google.com/file/d/1K4PEsITOHBPPk4vB129tIwvGnEi0JP1R/view?usp=drive_link

If it’s not there, can you please:

1. Enable WP debugging as per the article Debugging in WordPress – Advanced Administration Handbook | Developer.www.remarpro.com
2. Add above the LINK tag HTML comment <!-- HOMEPAGE BLOG POSTS HEAD CODE -->

and then let me know when you do that so I check your homepage again?

Thanks,
Aleksandar

Hello @unkfrank,

Thank you for choosing Head & Footer Code for your project.

Could you please provide a bit more details about the issue (screenshot is more than welcome).

Tested on latest HFC version as a part of BODY code on the page, and it works as expected – please check screenshot https://drive.google.com/file/d/10E1znjv-yQixHqXFxElMa2zHhgctkCHv/view?usp=drive_link

Thank you in advance,
Aleksandar

Thank you for choosing Head & Footer Code for your project!

Tha are great news, thank you for your confirmation.

If you don’t mind, feel free to review Head & Footer Code plugin

Cheers,
Aleksandar

Sure, because on the clean new website you also load your GTM container GTM-527QQ79, which has a Custom HTML tag (ID 42) which injects to page plain JS code:

function() { var filepath = https://www.facebook.com/.pathname.split("/"); var filename = filepath.pop(); var decodedFilename = decodeURI(filename); return decodedFilename.indexOf(".") > -1?decodedFilename:'n/a'; }

as you can see on screenshot https://drive.google.com/file/d/1aFYQTnYJXN3IMNEu9AZE6F3WdZZaRph2/view?usp=drive_link

If you remove the GTM container snippet from the Head & Footer Code, or pause the Custom HTML tag with ID 42 and publish the container, there will be no code injected when you click on target="_blank" links.

After all, are you okay to find Custom HTML tag with id 42 in your GTM container GTM-527QQ79 and provide screenshot of that tag content?

Thanks,

Aleksandar

Hello @hbna,

Thank you for choosing Head & Footer Code for your project!

Issue you experiencing is not caused by our plugin but prove that it works as expected (injects GTM tag on pages).

Anyway, make sure you wrap to the <script></script> the JS code in GTM Tag #42 within GTM container GTM-527QQ79 as that one injects to the page footer unwanted code visible to visitors:
https://drive.google.com/file/d/1MO1hoHkFLhMpaF1n6P3j31cB23ntyf8r/view?usp=drive_link

Please let me know if you have any further questions.

Aleksandar

Hello @toc123,

Please note that the latest version of the Head & Footer Code plugin is 1.3.3, and it does not support injection of the PHP code.

I would say you raised a support ticket for wrong plugin.

Thank you for understanding,
Aleksandar

Hi @xbor17,

I hope you are doing well. Not sure if you managed to resolve this issue, so I wrote a helper script to fix plain code in the database.

https://gist.github.com/urosevic/4001f130f81f98c19654ac3db31a0c6b

After you do regular import with the plain script code as a value for _auhfc post meta, run the above script. It will read all _auhfc post metas and if it’s not in HFC-compatible format do conversion and put plain code to the head section.

Give it a try on testing environment and let me know if that works for you.

Kind regards,
Aleksnadar

Hello @etextsrl,

Thank you for choosing Stock Ticker for your project.

Regarding the SYMBOL_SEARCH endpoint of the AlphaVantage.co API, Olidata is not in their database within any of the Stock Exchanges (check the screenshot linked below), so I suppose Alpha Vantage no longer supports BIT Stock Exchange.

https://drive.google.com/file/d/15EbZVJJ9Mv3gyaoG1Ddshn3iMW-6NK3l/view?usp=drive_link

Please refer to FAQ item Stock Exchange or Symbol I need does not work!

Kind regards,
Aleksandar

Hi @nicowebtotem,

Thank you for choosing Head & Footer Code for your project.

I would need to test HFC with WooCommerce and see what’s happening.

Meanwhile, if you do a standard WordPress export of “All Content”, does that XML file contain HFC metadata, something like the snippet below?

<wp:postmeta>
    <wp:meta_key><![CDATA[_auhfc]]></wp:meta_key>
    <wp:meta_value><![CDATA[a:4:{s:4:"head";s:27:"<!-- new blog post Head -->";s:4:"body";s:0:"";s:6:"footer";s:0:"";s:8:"behavior";s:6:"append";}]]></wp:meta_value>
</wp:postmeta>

Thank you for your patience,
Aleksandar

Hello @xbor17,

Thank you for choosing Head & Footer Code for your plugin!

I run quick test with default WordPress export/import for regular blog posts and pages, and that worked well.

I’m going to set up some custom post types on development environment and run more tests. Hope to get back with more info in a few days.

Thank you for your patience,
Aleksandar

Hi there,

I added this feature request to the GitHub repo to have it as a reminder when we get back to further enhance HFC, feel free to watch it for progress:

https://github.com/urosevic/head-footer-code/issues/2

Kind regards,
Aleksandar

Hello @mytrx,

Thank you for choosing Head & Footer Code for your project!

I could not reproduce issue you have reported on WordPress 6.4.1 with Twenty Twenty Four theme and Head & Footer Code 1.3.1. Screen recording is here https://drive.google.com/file/d/1eCoUuCB6nAi60y99dxOScR9UU25QDiTF/view?usp=drive_link

Can you please provide a bit more details about your WordPress setup (version, theme, do you have some caching plugin, can you record issue and provide screen recording)?

Thank you in advance,
Aleksandar

Hey @rosepac, thank you for choosing Head & Footer Code for your project and rating it with 5 stars!

I guess there was some ghost character in the code (eg. &nlbr; caused by a copy and paste around). I would appreciate it if you could provide that buggy code via pastebin.com so I check if detecting and fixing it on save is possible.

Cheers,
Aleksandar

Hi Jroy,

I highly recommend upgrading to the latest version 2.23.4 because all previous versions are vulnerable. Make sure you re-save plugin settings, just in case.

Please note, that Magnific Popup has been removed since version 2.23.0 and the original plugin version does not inquire about it. If you modified the plugin or made some customizations, you would need to update it to match the new HTML structure (eg. you targeting class ‘ytc-mfp-content’ from custom file wp-content/themes/phap/js/phap-script.js but in the new version that class does not exist anymore).

I would also appreciate if you provide settings of plugin and shortcode, so I try to replicate issue on my development stack.

Thank you for your assistance,
Aleksandar