Studiobovenkamer

Experiencing the same redirect loop on the log-in page. Running PHP 8.0.8. Locally, WP is installed in the root directory (not a subdirectory).

We don’t experience this issue on the live/hosting server which has PHP 8.0.28 installed.

Running version 2.9.5 of WP User Manager

• This reply was modified 1 year, 8 months ago by Studiobovenkamer.

Thank you for your quick reply. Unfortunately, I wouldn’t know how to do this. For now, my workaround is setting all posts that need to be excluded to draft status (for now these draft posts don’t need to be accessed by the user, so it works but it’s not ideal).

• This reply was modified 1 year, 9 months ago by Studiobovenkamer.

Thanks!

For other people looking for this information, here’s an example of how to add a custom taxonomy to the collection, show it as a facet and show it in your search results:

Formatting the data coming from the custom taxonomy (add this to the cm_typesense_format_sources_data funtion):

//Format custom taxonomy 
$customTaxonomyTerms = get_the_terms($object_id, 'custom_taxonomy');
$customTaxonomy = [];
foreach ($customTaxonomyTerms as $customTaxonomyTerm) {
    $customTaxonomy[] = $customTaxonomyTerm->name;
}
$formatted_data['custom_taxonomy_name'] = $customTaxonomy;

Adding your custom post type to the custom schema and showing it as a facet

...
['name' => 'custom_taxonomy_name', 'type' => 'string[]', 'facet' => true],
...

Displaying the custom taxonomy in your custom search results template:

<div class="hit-key-custom-taxonomy"><em>Custom taxonomy:</em> data.custom_taxonomy_name</div>

That’s it!

And another example of formatting a simple ACF textarea and adding it to the schema.

//Format ACF textarea field called 'textarea' inside a ACF group field called 'example_group_field'

$textarea = get_field('example_group_field
_textarea', $object_id);
$formatted_data['textarea_name'] = wp_strip_all_tags($textarea);

...
['name' => 'textarea_name', 'type' => 'string'],
...

• This reply was modified 1 year, 10 months ago by Studiobovenkamer.
• This reply was modified 1 year, 10 months ago by Studiobovenkamer.

Sorry for my typo: …”?but I canNOT figure out how to correctly format ACF fields like”

I’ve made the changes you suggested above on the 21st of March. It does seem to have effect on the direct hits, but it’s not clear if organic hits are now picked up correctly. I want to give it a couple of days and check it again.

@darrenburn when you say ‘that code’ you are referring to the exact code @esposito88 wrote in his post?

@esposito88 did you solve your problem by adding this list to the Cache > Exclude setting?

Sorry for the late reply, we needed some time before we could test this.
Unfortunately there was no change in the error reporting after using the updated version.

+1 to be able to remove custom capabilities in the Members plugin.

I think this is related. The latest version of iThemes security forces a jQuery enqueue somehow. This breaks functionality with some other plugins. This is the extra jquery call I see when iThemes 6.2.1 is active.

< script type=’text/javascript’ src=’https://&#8230;./wp-includes/js/jquery/jquery.js?ver=1.11.0′></script>

This gets enqueued even though default WP jQuery is deregistered.

• This reply was modified 7 years, 7 months ago by Studiobovenkamer.

Experiencing the same issue on WooCommerce shop page (which is also a custom post type).

Hi Vasyl,

Was this problem resolved? I’m running 3.0.9 and get the same warning:
Warning: Invalid argument supplied for foreach() in ../wp-content/plugins/advanced-access-manager/Application/Backend/Manager.php on line 87.

Warning: Invalid argument supplied for foreach() in ../wp-content/plugins/advanced-access-manager/Application/Backend/Extension.php on line 180

When visiting the AAM page in the admin I also get three alert pop-ups, all with the same warning:
DataTables warning: table id=role-list - Invalid JSON response. For more information about this error, please see https://datatables.net/tn/1

Opening the extension tab, there one more warning:
Warning: Invalid argument supplied for foreach() in ../wp-content/plugins/advanced-access-manager/Application/Core/Repository.php on line 224

I can send you a screenshot, but I’ll try to explain myself better so others don’t have to make the same mistake. What I meant to say was I solved my problem and it was just a show/hide option that wasn’t checked for the Editor in the Screen Options panel (upper right corner of the interface) on the Menus page. So this wasn’t a problem with configuring the AAM plug-in.

Detailed explanation
So I have a custom post type called Clients. I want the Editor role to be able to manage the menu’s and add pages/posts/clients to the menus. But the problem was that (after adding the capability Edit Theme Options to the Editor rol), I could only see the Pages/Posts/Custom Links as selectable options for the Menus. There was no option for selection posts from custom post types, although the admin role did see these posts).

This caused by an unchecked checkbox in the Screen Options panel in the upper right corner of the interface on the Menus page. So the Editor just had to open up Screen Options and check the checkbox ‘Clients’ (in my case) to show this custom post type as selectable menu-item option.

Sorry for wasting your time and thanks for your reply.

I already had the capabilities set correctly, but the editor role / user has the custom post type hidden by default in Screen options under Appearance > Menus.

Thanks for your immediate reply and explanation!

This is used to simplify the category access control cause you can group pages into categories and manage access to group of pages.

I understand the added functionality in using categories, but shouldn’t this be an opt-in option? As far as I know your plug-in doesn’t add anything (visible) when it’s activated and left default configured (which is good). You can flavour the options from there on, instead of having it flavoured for you.

Personally I don’t like it when stuff is added by default, which have to be turned-off again. I’d reckon the default of WordPress should be the starting point, so you can flavour it yourself.

But this is a usability/design decision you should make.