if you have the username/password for every user (i assume you are using this whole shebang somewhat internally ) you could create a order history page (i.e a page with [wppizza type=”orderhistory”] shortcode on it) and get a list of that particulars person orders.

however, as it stands, there isn’t really any integration of any kind to send this by email in a “click here to email” button sort of way#

the only thing i can think of is doing something like running the_content filter on that purchase history page along these lines

add_filter( 'the_content', 'my_the_content_filter', 20 );
function my_the_content_filter( $content ) {
global $post;
if($post->ID == x && is_user_logged_in()){//x being the post id of that page
$user = wp_get_current_user();
$user_id = $user->ID;
$user_email = $user->email;//or similar, dont know of the top off my head how to get the email, see codex
/* run a query on wppizza orders table using wp_user_id = $user_id and save as file somewhere perhaps*/

$content.='add some button that on click sends the file to user ';// 
}
    return $content;
}

the above is just a very rough idea, i am sure there would be more hoops to jump through to make this work, but should be doable

>I did debuging but it doesn’t work.
what exactly do you mean by “I did debuging but it doesn’t work.” ?

what does your debug log say ? (assuming you followed this https://support.wp-pizza.com/topic/how-to-enable-debug-in-wordpress/ )

ok, but what does that have to do with something hijacking the core WP thickbox though ?

more importantly if you want to use the redirect thing you want to have it opened anyway without having to click on a button first, don’t you ? (which is the default behaviour)

not sure where the issue is or why the behaviour it already has needs to be modified ?!

you are using something that hijacks the normal wp thickbox.
you have to re-initialize the map once the container has been opened (check the google codex re maps) or it has no idea what size it needs to be and the width/height is 0 – hence nothing shows

you will see what i mean when you open the container/map and simply resize the browser. it will now show up as the container div has a specified/known width / height when it’s opened

that wont work

you are supposed to remove the filter (and you REALLY need to understand how filters and action hooks work if you want to do any kind of customisation in wordpress – there are plenty of tutorials )

for the time being and simplicities sake (but be aware of the consequences of editing core files – i.e you will not be able to update the plugin without loosing your changes or having to re-apply them every single time). However i make no guarantees if you choose to do so:

in v2x.php of the plugin you will find (approx line 81)

add_filter('wp_get_nav_menu_items', array($this,'wppizza_tm_exclude_nav_menu'), null, 3 );/*exclude posts and pages from nav menu (appearance->menus)*/

simply delete that line (or comment it out)

let me re-iterate though. you are trying to use a program/plugin for something it was not designed for

btw, just to be sure, simply removing the filter on a test install works just fine and simply re-shows (so to speak) the pages/links that were omitted (you do seem to somewhat also have some post categories in your menu for some reason – i would suggest you re-check your Appearance->menu setup)

what shortcode ?
i did no say anything about shortcodes..

pages do not appear in the dropdown menu if there’s nothing on the pages that can be ordered because the time(s)/date(s) set for the items when they are available is outside the current time/date. that’s intentional.

however, you have chosen to not only display the items not available (that’s optional of course – under the options tab of the plugin), but have also overridden the css to actually allow ordering of the item.
that kind of defeats the point of using the plugin.

I guess I could add an option to NOT remove the pages from a menu if they are empty (i.e there’s nothing on there to order) but am somewhat puzzled why you would use the plugin in the first place ?!

perhaps I am missing something ?

PS: Btw, this has nothing to do with or is caused by the theme you are using with the plugin…

first of all, you need to enable debug and check the debug log
https://support.wp-pizza.com/topic/how-to-enable-debug-in-wordpress/

secondly, a 403 error is a server error you will have to investigate (but the debug.log might help)

as of wppizza version 2.16.11.24 , i believe this is now fixed and was due to some legacy coding left in the plugin for very old wppizza versions (in case anyone cares reading this :))

had nothing to do with WPML or any other non-wppizza plugins. simple coding error on my behalf

obviously, if there are still issues for some reason, let me know

PS: might take a couple of minutes for that update to show up in your plugins page