Forum Replies Created

Viewing 15 replies - 406 through 420 (of 530 total)
  • Plugin Author ulihake

    (@ulih)

    Hello fashionphotog.

    Hopefully you’ve solved your problem. I will close this as there’s no feedback from your side. If you still experience problems don’t hesitate to contact again. You can reply here over the next days as I will see your answer.

    Regards.
    uh

    Plugin Author ulihake

    (@ulih)

    Hello again Brendavo.

    I will have to take a closer look at the “WooCommerce PDF Invoices” plugin. As I want to implement such a plugin on one of my own sites, there’s a good chance that I will be able to answer your question within two or three days.

    Right now I have no idea if “WooCommerce PDF Invoices” exposes some filters to add captured order meta data to an invoice.

    So far, I can only give you a general hint. WordPress offers functionality to retrieve captured meta data for any post type and WooCommerce orders are posts of post-type order. You can use something like

    $meta_values = get_post_meta( $post_id, $key, $single );

    In the context of an order you would set

    $post_id to the order_id
    $key to the billing field using an underscore (billing_piegadatajs should be _billing_piegadatajs) and
    $single is optional and can be set to true in the context of billing and shipping fields in nearly any case

    This code should work once you fill in the correct variables or values:
    $order_meta_value = get_post_meta( [order_id], [_your_billing_or_shipping_field] );

    There are more functions in WP available to handle the captured data like get_post_custom().

    Hope this gives you an idea on how to work with your plugin. If the pdf invoice plugin offers some documentation on filters and actions you may be able to get this running yourself.

    Regards.
    uh

    P.S. I will close this but come back to you as soon as I’ve implemented something myself in this context.

    Plugin Author ulihake

    (@ulih)

    The code you expose does not belong to 2.1.5. It’s code belonging to a version below 2.1. The 2.1.5 html code inside variable.php reads:

    <button type="submit" class="single_add_to_cart_button button alt"><?php echo $product->single_add_to_cart_text(); ?></button>

    And the path 2.1.5 is:

    wp-content/plugins/woocommerce/templates/single-product/add-to-cart/variable.php

    It seems as if you mix up things from two Woocomerce versions and in these circumstances it’s quite impossible for me to help you.

    Regards.
    uh

    Plugin Author ulihake

    (@ulih)

    There’s another key question: Do you use a theme which is customized for WooCommerce? If so, please check if your theme includes a folder called woocommerce. It’s possible that the problem is related with outdated template files for woocommerce packaged with your template.

    uh

    Plugin Author ulihake

    (@ulih)

    Hello Gemma Wild.

    Thx for your feedback. I did a quick test just to be sure and I cannot confirm your statement. You can leave labels blank and they will not show up, at least on my test site.

    I need to know which WooCommerce version you are using and which Poor Guys Swiss Knife plugin version. Could you please facilitate this information.

    Thanks.
    uh

    Plugin Author ulihake

    (@ulih)

    Hello rosso711.

    Seems that you’re still using WooCommerce < 2.1 and one of my last updates may have broken the support for add to cart button labels for installations < 2.1… I will fix this.

    uh

    Plugin Author ulihake

    (@ulih)

    I will implement this… it’s on my list… but I don’t know if it will make it into the next update… maybe you have to wait two or three weeks to have this feature available.

    uh

    Plugin Author ulihake

    (@ulih)

    You have to configure the field. The type column reflects for custom fields buttons which allow you to access the configuration options…

    Please let me know if this fixes your problems.

    uh

    Plugin Author ulihake

    (@ulih)

    Hello tzeldin88.

    Probably next weekend.

    Regards.
    uh

    Plugin Author ulihake

    (@ulih)

    The next update will allow you to enter an empty value line into the select configuration which won’t convert to a checkbox or radio button, leaving all resulting radio buttons and checkboxes unchecked.

    Regards.
    uh

    Plugin Author ulihake

    (@ulih)

    I’ve tested this and that’s not working. You’re right. The jQuery part only works in the wcpgsk-user.js. I will provide a fix for this with the next update. In the meantime you will have to use the wcpgsk-user.js and backup the contents when you update the plugin the next time.

    uh

    Plugin Author ulihake

    (@ulih)

    You could replace:
    _postServiceOption.value = _psTerminal.id;

    with:

    _postServiceOption.value = _psTerminal.id + ' - ' + _psTerminal.name;

    in your javascript code. This will combine the id of the post station with the name into the value… and will display as e.g. “3 – Whatsoever station”.

    uh

    Plugin Author ulihake

    (@ulih)

    Yeah, a whole lot of things would be great, but that’s available for you already. You have some custom key pairs (value/text) and I offered you the possibility to load these key pairs into an empty select field that is recognized by WooCommerce. I’m not responsible for the value/text combination: this is your data! The value can represent something meaningful to a human or it can represent a number, a code that is meaningful only to an interpreter and it can be a mix of both, like I indicated to you. To automate external data handling that is different from data provider to data provider is not the goal of my plugin. It’s up to you to assure that your data complies with your expectations.

    To put it clearer. Exactly for this reason you can hide some data from display and it’s your decision to add a custom field and to display the selected value. If you want the value to be comprehensible to humans you have to provide such a value. WooCommerce itself does not display for instance the country selection value as the value would show up as es_ES for example.

    For sure, it’s possible to remap a value to a corresponding text but once again, that’s far behind of the scope of the plugin at this moment and if I implement something like this it will be a feature of the Rich Guys Swiss Knife.

    If you’d like to fix this, adapt your javascript code. I tested your code both in wcpgsk_user.js and inside of the storage field for script snippets in the checkout section and it’s possible to get this solved. If you want to reconfigure the value you only have to change one line in your javascript code that configures the value/text pairs of the select.

    uh

    Plugin Author ulihake

    (@ulih)

    Hello Brendavo.

    That’s like this since the days internet exists. If you specifiy a value for an option the posted value will be the option value. If you do not specify a value for the option, the posted value will be the text of the option.

    On your side you will need the number, on the client side it would be nicer to display the post station, I agree. What you can do is once again a JQuery modification of your values… e.g. joining value and text for the value (value=”3 – Post Station somewhere in nowhere”), if this is suitable for you in the back-end.

    All what you need is already in your code… 🙂

    uh

    Plugin Author ulihake

    (@ulih)

    well, that’s something I’m doing, that’s right… There’s only one select type which can be displayed as dropdown, multiple select, checkboxes, radio buttons… the display is configured client side via jquery.

    Regards.
    uh

Viewing 15 replies - 406 through 420 (of 530 total)