oivind

Aha, It have to install fail2ban separately.
Thank you!

Great Vinny! Your the man!

I also have this problem, It seems its not related to my theme because before I ugraded woocommerce to >3.0, woocommerce rendered html from the order item meta just fine.
(I also upgraded dopbs plugin to version 2.7.5 that should be compatible with woocommerce 3.0 to check if that would help, but that did not have any effect)

The change in woocomemrce in order-details-item.php:

do_action( 'woocommerce_order_item_meta_start', $item_id, $item, $order, false );
//woocommerce 3.x:
			wc_display_item_meta( $item );
//woocommerce 2.x:
			$order->display_item_meta( $item );
do_action( 'woocommerce_order_item_meta_end', $item_id, $item, $order, false );  

If I use the old woocommerce method it renders the reservation details with html from dopbs plugin, but with woo depreaction notice.

If I use the new method the html is stripped and it looks pretty much like the screenshot that capnjazz provided.

Also, I am using actions and filters to modify the billing / customer details:

woocommerce_email_customer_details
woocommerce_checkout_fields
woocommerce_checkout_update_order_meta

But I cant control the data that will enter into the order displayed in the wp-admin -> woocommerce -> orders

What are the filters / actions to do that?

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

No, I left image directory settings untouched, and yes, i can upload to media library so the “upload” folder is writeable. I’ll send you an email later

Sorry, heres the url for the image: https://imgur.com/dFTwig6

Thanks,that cleared some parts for me!
Though it could seem as we have faced the same problem.
I saw the changelog:
= 1.0.5 =
* Hide image caption field

That fix do not adjust the modal height to fit, so there’s a gap where the caption field was.

Maybe you did not bother the extra space, I can understand that, but for me, removing 3 fields and not readjust height afterwards is unfortunately not an option.

Thanks for the plugin!

Hi, I’ll try to expand the explanation.

First find this file in the dopbs plugins folder: ‘class-frontend-calendar.php’

In this file we will make a new variable $view. Add it after the $language variable, like below:

$language = $atts['lang'];
//create new variable here:
$view = $atts['view'];

Then some lines further down:

//BEFORE:
//'view' => $settings_calendar->view_only == 'true' ? true:false),

//AFTER:
'view' => !isset($view) ? ($settings_calendar->view_only == 'true' ? true:false) : ($view === 'true' ? true:false) ) ,

( notice the commas! )

RESULT:
Then you can use a shortcode looking like this:
[dopbsp id=1 view=true lang=no]

Hope it helps!

For posterity, here’s the fix:

in class-frontend-calendar.php:

//find:
$language = $atts[‘lang’];
//create new variable:
$view = $atts[‘view’];

…
// change this:
//’view’ => $settings_calendar->view_only == ‘true’ ? true:false),

//to:
‘view’ => !isset($view) ? ($settings_calendar->view_only == ‘true’ ? true:false) : ($view === ‘true’ ? true:false) ) ,

Now you can use ‘view’ as a shortcode attribute.

I’ts okay, I managed to fix it.

I have to add to the last post that the solution I’m referencing was intended to fix the “licenses Stripe settings template”. But the same solution worked to fix my problem with “Stripe settings template”.

in file [..]/views-stripe-backend-settings.php

Here is the change in the method

FROM:
<a href="DOPBSP.toggleInputs('stripe')" ...

TO:

<a href="DOPBSPBackEnd.toggleInputs('stripe')" ...

So, I found a five month old support thread giving me a better fix.

https://pinpoint.world/wordpress/support/forums/topic/plugin-will-not-display-in-licenses-section-to-enter-license/

I see that you have not updated the stripe gateway addon since 17 feb. 2015. This has been an issue at least over five months!

There, finally I could access the stripe addon settings. The problem was not that the stripe addon in it self. The settings fields was just hidden with a css class set to display:none.
https://imgur.com/8Dzlftv
So it works! I can move on!

Could this be related to the other css problem with the icons in wp-admin? Since I could not click to expand?

Ok, i giggled a little…. ??