hivizwebsolutions

So the stylesheet/script inside the CSS/JS snippet is already enqueued by the way this plugin is designed. Got it.

Will now close this ticket.

Actually, upon further investigation, I think my original question was misguided. I can see that anything put in a CSS snippet is loaded into a separate “query-string-modified-homepage file” (of the form: yourdomain.com/?code-snippets-css=1), and anything put in a JS snippet is loaded into, yet again, a separate “query-string-modified-homepage file” (of the form either: yourdomain.com/?code-snippets-js-snippets=head or yourdomain.com/?code-snippets-js-snippets=footer, depending on the load location).

So when you say:

If you add CSS or JS snippets, they are enqueued for you using?wp_enqueue_*?and an automatically generated src URL.

…do you mean that anything put inside JS snippets are loaded into the aforementioned “file”, and then enqueued via the wp_enqueue_scripts function and hook, something like this:

function my_scripts_method() { 
    wp_enqueue_script( 'my-script', get_home_url . '/code-snippets-js-snippets=header'); 
} 
add_action( 'wp_enqueue_scripts', 'my_scripts_method' );

Custom ordering, like what ACF allows, would be great.

Hi Shea,

Just following up on this ticket.

Many thanks!

Issue can be circumvented with v2.04+ by switching off “Typo” setting under Manage Extensions: https://prnt.sc/KsioNkBMyD5L

Thanks Shea, will now close this ticket.

Thanks Shea,

Your response addresses the question: “what is the scope of the backend ‘admin area'”; my question was more regarding the scope of the frontend ‘public facing area’.

In the same way that is_admin() determines the backend, what function determines the frontend?

Many thanks!

Thanks Shea,

* “Essentially, it works just like a regular snippet, except after you ‘activate’ it and it executes, it deactivates itself again immediately.” << In that case, I can’t explain the behaviour I’m observing on my website. I have a piece of code that redirects logged-in users from the home page to a different page: https://prnt.sc/ksqSyd0d-1NP

What I observe is that any logged in user will get redirected to the page specified when they try to access the home page…each and every time, which means that the code is not deactivated after it is saved.

What am I missing in my understanding?

Thanks Shea,

I see. For (my) better understanding, could you please also help me with the following:
* What is the scope of “run once”? Both backend admin area and site frontend? One or the other?
* What is the “trigger event” (for the code to run exactly once)? When the snippet is saved and activated? Something else?
* What happens if another user logged in and activated the same trigger event? Would the code still run? Or is there “global memory” that the code has run once and will therefore never be run again, whether or not a different user activates the same trigger event?

Many thanks!

Thanks Amimul,

How do I check the email header? I am using the PC desktop app for Outlook.

Many thanks!

Thanks Amimul,

What I don’t understand is that the setup consists only of FluentSMTP, and I’m using the Test Email feature provided by the plugin itself – nothing else. And yet, the test email lands in spam (see screenshot link in opening ticket).

I would assume that the test email that the plugin is sending is not a spammy one, and so the fact that it lands in spam, to me, suggests that the plugin itself is not functioning correctly.

Can you please speak to this point?

Many thanks!

Thanks Shea,

* “If you add CSS or JS snippets, they are enqueued for you using wp_enqueue_* and an automatically generated src URL.” << Can you provide an example of such an auto-generated src URL?

* “Can you clarify what situation you are using wp_enqueue_script/style in?” << This is a specific example. In the tutorial, the main function is saved as an external script sheet called “global.js” which is then enqueued.

Many thanks!

Thanks Shea,

Your example clarified my confusion, much appreciated.

Will now close this ticket.

Many thanks!

Thanks Shea,

1) Thanks for clarifying the difference between template_redirect and wp_head in that the former executes before page load and the latter, after.

2) Yes, still working on it; would appreciate a clarifying (contrived) example that highlights the rationale behind why the acf_form function is placed between the output buffering functionality.

Many thanks!

Thanks! Will now close this ticket.