netzgestaltung

HA, nevermind.

I have added the ‘the_content’ filter to excerpts on pages for other reasons.

I now use the members_can_current_user_view_post() function from /inc/template.php to see which filter i apply there und the above code does work exactly as expected.

• This reply was modified 3 years, 10 months ago by netzgestaltung.

happy i could help (and get an update ?? )

hi there, i got the same message. i think since 1 or 2 days or so.

I also gut more messages to share, so you might find the issue which i think is related to the last WP updates (so you should look what have changed)

This shows in the backend:
Notice: Undefined index: honeypot_cf7_req_msg_dismissed in /wp-content/plugins/contact-form-7-honeypot/includes/admin.php on line 23

These are visible in the frontend:

Notice: Undefined index: placeholder in /wp-content/plugins/contact-form-7-honeypot/includes/honeypot4cf7.php on line 61

Notice: Undefined index: w3c_valid_autocomplete in /wp-content/plugins/contact-form-7-honeypot/includes/honeypot4cf7.php on line 65

Notice: Trying to access array offset on value of type null in /wp-content/plugins/contact-form-7-honeypot/includes/honeypot4cf7.php on line 76

maybe its also related to caching?

The settings page was also full of errors, screenshot:
https://office.netzgestaltung.at/index.php/s/C2zzSmS4CJc4XoL/preview

after resetting and saving its gone.

I also encountered more errors

when adding a collection field inside there is another “add” button that does not work.

also on editing related content in posts in the block editor (i also quick-fixed that one with another PR)

you need to check every “.on” function if the preceding selector selects an element that is added to the DOM later in time.

br
tom

• This reply was modified 4 years ago by netzgestaltung.

I made a pull request for that, compare the changes: https://github.com/aprokopenko/justcustomfields/pull/96/files

the (temporary) fixed file: https://github.com/netzgestaltung/justcustomfields/blob/netzgestaltung-patch-edit-field-js/assets/just_custom_fields.js

please be aware that updates will overwrite your changes in plugin files.

Ok i fixed it in my instance.

the problem is inside the JS construction at `/just-custom-fields/assets/just_custom_fields.js

before there was the old live function for the submit event handler of the “edit field” form. it took care of elements with the same selector to be attached to the event handler even if its created after the attachment (by an ajax call) which is the case here.

i encapsuled the event handler in a new seperate function jcf_init_edit_field apart from initFieldsetFields and added it to the promise handler of the ajax response jcf_show_ajax_container

i will make a pull request on github and share the changed code when its ready.

• This reply was modified 4 years ago by netzgestaltung.

i can confirm that.

currenty im exporting/importing the json to add fields. but i don’t know how a table field should look like.

im glad that an update will content that changes!

i now found that this was only the “plugin exists” question, the rest of the code only uses database entries that seem to not have changed (good).

i changed the occurances in my code:

before
function_exists('wpcr_avg_rating')

after
class_exists('WP_Post_Comment_Rating')

and now it looks working again.
I will test it now with new ratings and orderby rating

• This reply was modified 4 years, 1 month ago by netzgestaltung.

wrondg thread

• This reply was modified 4 years, 2 months ago by netzgestaltung.
• This reply was modified 4 years, 2 months ago by netzgestaltung.

Hi there,

its the same issue as for https://www.ads-software.com/support/topic/swipebox-and-jquery-3-5-x

swipebox itself is not compatible to jQuery 3.x.x to which WordPress updated with 5.6

also look here:
https://www.ads-software.com/support/topic/website-goes-blank-swipebox-overlay

• This reply was modified 4 years, 2 months ago by netzgestaltung.

Check the inspector inside the browser, network tab, filter to only JS files and look where the location of jquery.swipebox.min.js is.

Swipebox seems not jQuery 3.x.x compatible which now is the WordPress used version, look: https://github.com/brutaldesign/swipebox/issues/379

Someone has support to swipebox in a fork (3 years ago):
https://github.com/mho79/swipebox/
if you have control over the used libraries you can test to replace it.

so the main project seems dead.

i walked trough the file cf7-2-post-taxonomy-metabox.php and reformated the code but its too weird for me. Why do you distinguish between published and draft post? Also you use various factories to get taxonomies.

If there are bugs in the back, its currently not debugable for me.

At one time your if condition for $is_new_mapping is $factory_mapping->get('map') and later you use !$factory_mapping->is_published('boolean', false).

I also can imagine that $taxonomy_slug = sanitize_title($factory_mapping->get('singular_name')) . '_categories'; gets you wrong results and saves wrong taxonomy slugs.

when i look in a draft at a new created taxonomy connection to an existing taxonomy the select id for the hook is: select2-cf7_2_post_map_taxonomy_value-lernmaterial-hochladen_categories-bc-container but the hidden form shows: cf7_2_post_map_taxonomy_names-projekt so the JS seem to not filter all names well to the selected taxonomy name. maybe it also gets stored wrong. i uploaded the file as gist so you can see my edits:
https://gist.github.com/netzgestaltung/8baa08712b245bc01080336fdfc562ec

No, no JS errors on that page.

I try to investigate it more, i can invest about 3hours.