ucfknight10

in the definition of my_custom_function, you’ll want to grab the variable $post or $id, using global $id,$post;. from there, you can determine the post type

what is the output of $mitglied ?

try this function, and see if it works for you.

https://csstyle.pastebin.com/S1r3J1nZ

https://codex.www.ads-software.com/Function_Reference/add_meta_box

ask the plugin author

to do this for immediate children is quite easy, but if you have pages that are nested several layers deep, you’ll need to write a function with a recursive conditional, to determine if the page is indeed a child of “work”.

well, i’m out. aside from actually sitting down and working through it, i’ve got nothing else to suggest.

you may want to take a chance, and learn a bit more about how wordpress works. tear it apart, touch it’s insides. ?? to diagnose your problem, open up wp-login.php, and follow it’s path of functions and commands. having a powerful search program will help locate function definitions and such.

oh. well, i’ve used it on several installations above 2.7, and havent had any problems with it.

ok, next step is to figure out where the error is actually occurring. i’m assuming you are familiar with php and wordpress. you need to find the code that processes the login, and create some sort of method of determining where the script actually get’s caught.

it can be something as simple as echoing your way through the alphabet every few lines of code (when it makes sense), or something more elaborate. just make sure you call the exit function at some point, to keep the script from redirecting back to the login page.

you may want to take a look at the plugin timber. it collects errors and displays them in the backend. it would be a good source of information for you.

ok. after logging in, and it redirects you back to the login page, manually type in the path to the admin (wp-admin). when i had this problem, sometimes it would work.

hmm, i am kind of at a loss as to what the problem could be then.

one last thought: try disabling your password protection on the folder, and see if it works then. i’m not saying it will, but let’s just be sure that it’s not interfering.

in wp-config.php, enter this code

define('WP_DEBUG',true);

and see if it generates any errors.

Mark’s solution is def better. Thanks Mark.

ok. open q-and-a.php, find in the function definition of create_qa_post_types the call to function register_post_type. you’ll see an array, with labels ‘labels’, ‘public’, ‘show_ui’, etc. go to the line starting with ‘supports’ (line 57), and add a comma to the end. add a new line, and copy and paste the code below into the blank line (now line 58).

'show_in_menu' => (is_admin_login() ? true : false)

when you’re done, the function call should look like this:

register_post_type( 'qa_faqs',
		array(
			'labels' => array(
				'name' => __( 'FAQs' ),
				'singular_name' => __( 'FAQ' ),
				'edit_item'	=>	__( 'Edit FAQ'),
				'add_new_item'	=>	__( 'Add FAQ')
			),
			'public' => true,
			'show_ui' => true,
			'capability_type' => 'post',
			'rewrite' => array( 'slug' => 'faq', 'with_front' => false ),
			'taxonomies' => array( 'FAQs '),
			'supports' => array('title','editor'),
			'show_in_menu' => (is_admin_login() ? true : false)
		)
	);

make sure you add the function i provided above to the plugin at the top, or in your theme’s functions.php. also note, that if you upgrade the plugin, you will have to make this change again (tho it may be different, seeing as how there are usually changes to the code when an upgrade is available).

hope that helps.