Forum Replies Created

Viewing 15 replies - 256 through 270 (of 564 total)
  • I commend you on trying to do this, however, I think it is far more complicated than just switching it out. I say this because I’ve been working on how to use V5 in a theme. The issue is that there are many other plugins our there that that are all using FA V4. The shim provided by FA does not correct all of the issues that replacing FA with V% using JS SVG. Trying to use 4 and 5 together breaks things equally as well. I’ve also found that trying to remove V4 completely as impossible because of the non standard ways that plugins enqueue it. for example, in the footer.

    I’d be interested in knowing how you work out any of these problems.

    Thread Starter John Huebner

    (@hube2)

    changing it to shop only changes /product/ to /shop/ and does not add /shop/ before category links. I’m looking to change urls for all WC pages, categories, products, etc to include /shop/

    What I have is 2 separate installations of WP, one for the site and one for the shop. This is, well, let’s say that I would not have built the site this way and I can’t see any reason why it was.

    We now want to combine the two into one WP install but keep the url structure as it was. I’m sure it’s possible, but I’m equally sure that none of the settings available will get us were we want to go and that I’m going to need to add some custom filters and or rewrite rules to accomplish this. I was just hoping that someone had some advice or links that would save me some time.

    From my communication with the developers I don’t believe that they are planning to add this to the plugin. I have made improvements in my “Add On”. As far as I’m aware it works well with all of the WPForms fields. It could use more testing. I have plans to make some minor improvements. I don’t see any reason that it will not continue to work into the future as long as there is not a major change in how WPForms detects that a form was submitted. It could probably stand a little more testing. https://github.com/Hube2/wpforms-ajax-submit

    Thread Starter John Huebner

    (@hube2)

    Yes, the number needs to match the post ID of the pardot form. This is where the filter is used in the pardot plugin

    
    return apply_filters( 'pardot_form_embed_code_' . $args['form_id'], $body_html );
    

    It means that each time a form is added that you need to add more filters. A generic hook would be better. Or even more hooks that let you adjust specific parts of the form rather than parsing html. But I guess it is what it is.

    Thread Starter John Huebner

    (@hube2)

    Thanks, That’s what I was looking for. I’ve put filters in place. I currently have ACF options pages to hold the values for these pages so that clients can manage it themselves. I’ll watch for changes to this plugin and change it when I need to.

    Thread Starter John Huebner

    (@hube2)

    Thanks, that’s all I needed to know. I don’t have a problem building something to sort the but I didn’t want to build something if it already existed.

    Thread Starter John Huebner

    (@hube2)

    I didn’t expect that, just really wanted you to be aware of the problem.

    I think that the compatibility issue with other problems could probably be handled by using a standard “handle” for the scripts of “select2” instead “wp-customer-reviews-select2”. The compatibility problem is due to trying to load multiple copies of the same script.

    As far as the local copy, I wasn’t expecting that right away. I just wanted you to consider a local fallback of scripts if the CDN is unavailable for some reason.

    I’m currently looking at several potential plugins for doing reviews. Honestly, I find yours the most promising but I really need the features listed for the “Pro” versions that you haven’t released yet.

    Plugin Author John Huebner

    (@hube2)

    post <=> user relationships would need an entirely different set of rules since the relationship would be in multiple tables post_meta, user_meta, etc. Then there is the inevitable request for user <=> user, post <=> taxonomy, taxonomy <=> taxonomy. All of these are probably completely possible. Unfortunately though these things are not something I have a great deal of time to add at the moment. Possibly at some time in the future.

    This plugin is on GitHub and I would welcome others contributing to it as long as the scope of what this plugin is meant to do does not creep to far. The main problem here is that once a feature is added to this plugin then it will likely fall on me to maintain that feature, something else I don’t have a lot of time for. As it is, there isn’t really any maintenance required on this plugin since the operation of post objects and relationship fields in ACF is not likely to every change…

    on the other hand, there is gutenburg coming up so all bets could be off.

    Plugin Author John Huebner

    (@hube2)

    Yes, this plugin can do this

    You create a filter to determine the email address to send to, see the instructions
    1) you create a hidden field in your form that has the field name “dynamic-mail-to-filter” and the value of the name of your hook, see the instructions
    2) create another hidden field with the name “dynamic-mail-to-fields”, the value of this field is the name(s) of the field that you want passed to your filter, (i.e the field that holds the ID value in question (see instructions)
    3) Create your filter that determines the email address to use based on the value of the hidden field that holds the ID in question, see instruction.

    The real question is why am I getting 4.5 deprecated warnings when running 4.4.9?

    Plugin Author John Huebner

    (@hube2)

    Sorry, I don’t understand what you’re doing, but it sounds like you are looking to have a field updated besides the relationship field. If that’s the case, this plugin will not do that.

    Plugin Author John Huebner

    (@hube2)

    it shouldn’t matter, try moving the new ... line to after the class code.

    Unless you have something else going on. However, it should not matter if you instantiate the object before or after the class is include unless your functions.php file is loaded in a way I’m not familiar with.

    With the fields you’ve created the non-oop code should also be working. If you use this code, is the filter running? If you put a print_r… die statement in it do you get the output?

    Plugin Author John Huebner

    (@hube2)

    you have this line commented so the object is never instantiated

    
    //	new wpcf7_dynamic_mail_to_examples();
    

    or you can try the non OOP example that’s included (and commented out) in the same file.

    Plugin Author John Huebner

    (@hube2)

    exactly what did you put into your functions.php file

    Plugin Author John Huebner

    (@hube2)

    Actually, that’s where I thought this was in the beginning. After your first comment when I clicked the link in the email WP told me the page could not be found. After the second I hunted it down.

    I originally built the three CF7 plugins I have to work together. The dynamic select field to allow a dynamic select field for “Subject”, the dynamic recipient plugin to send emails based on the subject selected and the hidden field to allow me to specify the hook of for the recipient field and allow supplying additional argument.

    Sorry about the documentation being confusing. They are all relatively simple plugins, but can be extremely powerful used in concert. The explanations only outline the simplest of uses.

Viewing 15 replies - 256 through 270 (of 564 total)