Shannon Little

Yes, I’m still getting the same log message, although it has moved from line 382 to 386.

[26-Jan-2024 17:37:15 UTC] PHP Deprecated:  Automatic conversion of false to array is deprecated in /var/www/html/public/content/plugins/instagram-feed/inc/Builder/SBI_Feed_Saver_Manager.php on line 386
[26-Jan-2024 17:37:15 UTC] PHP Stack trace:
[26-Jan-2024 17:37:15 UTC] PHP   1. {main}() /var/www/html/public/wp/wp-admin/admin.php:0
[26-Jan-2024 17:37:15 UTC] PHP   2. do_action($hook_name = 'load-instagram-feed_page_sbi-feed-builder') /var/www/html/public/wp/wp-admin/admin.php:237
[26-Jan-2024 17:37:15 UTC] PHP   3. WP_Hook->do_action($args = [0 => '']) /var/www/html/public/wp/wp-includes/plugin.php:517
[26-Jan-2024 17:37:15 UTC] PHP   4. WP_Hook->apply_filters($value = '', $args = [0 => '']) /var/www/html/public/wp/wp-includes/class-wp-hook.php:348
[26-Jan-2024 17:37:15 UTC] PHP   5. InstagramFeed\Builder\SBI_Feed_Builder->builder_enqueue_admin_scripts('') /var/www/html/public/wp/wp-includes/class-wp-hook.php:324
[26-Jan-2024 17:37:15 UTC] PHP   6. InstagramFeed\Builder\SBI_Feed_Saver_Manager::maybe_feed_customizer_data($include_comments = *uninitialized*) /var/www/html/public/content/plugins/instagram-feed/inc/Builder/SBI_Feed_Builder.php:484

It was happening just viewing the Chart Library page, but for anyone else who comes across this ticket, the issue has been fixed as of version 3.10.6. Works fine in PHP 8.3.2 too.

I haven’t seen any functional issues aside from the log messages. I just tested it in PHP 8.2 and 8.3 and didn’t see any new issues ????.

Currently using version 6.2.7

I just ran into the same issue, different hosting (AWS). For me the issue was the rename of v2_Views.php to V2_Views.php. My site is deployed using git and for some reason my git had ignorecase = true so the rename wasn’t captured. Once I fixed it, it was working.

Hi,
You can’t trust the inspector here, it shows the DOM after it has auto-corrected errors and normalized the markup. If you view the source code, then it’ll be visible (Firefox highlights errors in red). I’m currently only using the pie chart.

https://i.postimg.cc/DZSN7sDF/Screenshot-2022-04-18-135100.png

Thanks, that was what I needed to know!

Thanks for the reply.

> The information that is available via the WordPress REST API is already available to the public via other means

While this might be true on a blog website using a stock theme that came with WP, it’s not true where WP is being used as a CMS on customized sites. Even your own plugin disagrees with the /users/ endpoint being freely available as it’s blocked by default for anonymous users. I have CPTs that are for internal uses or used as part of bigger blocks, and I have to enable the REST API for them for the block editor to function. I’d rather not leak info about any parts of the infrastructure I don’t have to.

As a test I’ve re-enabled the REST API and successfully connected it to WF Central. During the process I notice it exchanged some PKI keys. Does this mean it no longer needs anonymous REST access to function correctly?

> Ultimately, Wordfence Central requires access to the REST API for users who aren’t logged in

It can’t need access to everything. The details it shows in the Central Dashboard are only available to auth’d users.

Make the username bold? I don’t think the current username needs to be highlighted at all.

@katekathy I’ve had the exact same experience with v3.x of this plugin and have rolled my back to v2. V3 has many, many issues and is bloated. I’m already looking for a better plugin.

Same issue here.

In the admin I can see the checkbox and button to edit the focal point, but they do nothing. Also the full resolution image is being displayed. I used a lot of high res images and the image went right off the screen.

I just came across the same issue and added notes to the codex entries for WP_Query and pre_get_posts about the is_singular issue. I don’t know how to update the docs at developer.www.remarpro.com, those seem locked down.

I got around the problem by using the posts_clauses filter and doing what the code at line 1960 would of done.

public function filter_posts_clauses( $clauses, $query ) {
  if ( !$query->is_main_query() || empty( $query->query_vars['custom_query_var_foo'] ) ) {
    return $clauses;
  }

  $tax_query = array(
    array(
      'taxonomy'         => 'foobar',
      'field'            => 'slug',
      'terms'            => $query->query_vars['custom_query_var_foo'],
      'include_children' => false,
    ),
  );

  $tax_query   = new \WP_Tax_Query( $tax_query );
  $tax_clauses = $tax_query->get_sql( $GLOBALS['wpdb']->posts, 'ID' );

  $clauses['join']  .= $tax_clauses['join'];
  $clauses['where'] .= $tax_clauses['where'];

  return $clauses;
}

Much appreciated!

Hi,
Is there any update on this?

It’s most likely a theme issue. I’ve not seen any issues with Edge using Redux.

I’ve always used TGM to have my themes require Redux Framework be installed alongside it.

If you use the embedded method, the only way to get updates is to install the Redux Framework plugin normally, then it’ll be used instead of the embedded version.

If you plan on selling your themes at places like Themeforest, they won’t allow you to use the embedded method.