mikehermary

@bcworkz Thanks for the reply and for pointing me in a helpful direction.

I identified the issue as a get_posts() implementation in a template partial that was executed before the main loop and was not using setup_postdata( $post ) at the start of the foreach and a wp_reset_postdata() after the foreach had completed.

After making this change, the main loop is now working as expected.

Cheers,

I have done some further testing and have included those results below.

I have tested $query = new WP_Query( array( 'post_type' => 'page' ) ) and outputted the $query using print_r(). The correct output is displayed for all of the pages on the child site (multisite). It also works when I add a specific page ID to the query $query = new WP_Query( array( 'post_type' => 'page', 'page_id' => 128 ) );

I have checked my functions.php file for any pre_get_posts, $query, or WP_Query code, but none exists. The $post is used for various admin section-only functions, so I do not see a conflict there.

Thanks for reply.

We will need the add-on for the options pages functionality, so we will get that purchased in the future.

Cheers,

Thanks for the reply and sharing the snippet.

I need some clarification regarding the snippet:

1. Does the blogs array require me to enter all of the IDs used for child sites on the network? The in-development website will have around three hundred child sites that would be connected by a numerical region stored in an ACF field. Or can it be captured using a dynamic value?
2. I have created a custom field (ACF) called “Region” and have attached it to both Posts and Options sections. The meta_key and meta_value of a specific region number were hardcoded into the function, but only worked when connected to Posts and not Options. Should this functionality work on ACF Option pages?
3. When testing a broadcasted post, nothing is displayed in the Broadcast column on the posts listing screen after being handle programmatically. Is this the expected result?

Cheers,

Thanks for the reply.

I assume this applies to the non-commercial version of the plugin as well.

Cheers,

• This reply was modified 1 month, 1 week ago by mikehermary. Reason: Fixed grammatical error

Hello Mikko,

Thanks for answering the question. I will direct any further questions through your website.

Cheers,

Hello,

Thanks for the reply. Would you recommend running the bulk optimization at a lower traffic period on the website?

Cheers,

Hello,

The table has been published as a csv and is working now.

Cheers,

Hello,

Thanks for the prompt reply and the answer.

I will get the client to publish the sheet and will let you know if the issue is resolved.

Cheers,

Hello,

Thanks for the reply and information. I had already added that code to the .htaccess file within the wp-admin directory. It did not solve the issue with loading the editor on the front-end without errors.

I was able to resolve the issue by creating a .htaccess file within the wp-admin > js directory and placing the following code within the file.

<Files "editor.min.js">
    Order allow,deny
    Allow from all
    Satisfy any
</Files>

This code removed the 401 errors and eliminated the browser login prompt. This is probably not the correct way to resolve this issue, but I needed to launch this functionality on my client’s website, so I went this route.

Please advise if there is a better way to resolve this issue.

Cheers,

Hello,

Update: it looks like Apache2-based password protection on the wp-admin directory is the culprit.

I have temporarily removed it and the form is loading on the front-end with no issues. I have included the code from virtual host file for reference below.

<Location /wp-admin>
    AuthType Basic
    AuthName "Restricted Content"
    AuthUserFile /etc/apache2/.htpasswd
    Require valid-user
</Location>

This surely is a bug as I need to keep the wp-admin directory protected.

Cheers,

Hello,

I have resolved this issue by moving the CSS into my theme’s CSS file. I had forgotten that I had disabled all Forminator CSS while the theme was in development.

Cheers,

Hello,

I have resolved the issue. I needed to add 'public' => true to the arguments for the CPT plugin.

Cheers,

Hello,

Thanks for sharing the code.

I have added to the code the custom CSS field, but it is not working while viewing the form preview or when it is embedded on a hidden page.

The custom CSS does not seem to be rendered in the HTML anywhere on the hidden page. I tried searching for it, but it did not appear.

Cheers,

Hello @julesomattic,

I reconnected JetPack and everything looks to working correctly now.

Thanks for your assistance!

Cheers,

• This reply was modified 1 year, 7 months ago by mikehermary. Reason: Marked thread as resolved