Forum Replies Created

Viewing 15 replies - 106 through 120 (of 234 total)
  • Hi.

    I’ll look into this, and made an issue out of it.

    The example code you posted, it seems like the forum here, rendered parts of it instead of displaying the code (the links: get our newsletter, and always stay updated….), which means I can’t see the entire snippet as you have it. Do you think you can repost it as code here (use the code tag) or on the issue thread linked in this post, so I can replicate your code exactly.

    Cheers,
    Johan

    Plugin Contributor Johan Steen

    (@artstorm)

    That is a completely normal behaviour. The blank pixel is used by PayPal to collect statistics among other things.

    You can disable it under Advanced -> Disable PayPal Statistics.

    Cheers,
    Johan

    Hi,
    Title: test
    Snippet: this is my shortcode
    Under variables, check the Shortcode checkbox.

    Done.

    Use the shortcode in posts with [test] or press the Post Snippets button in the post editor to insert it that way.

    Cheers,
    Johan

    Plugin Contributor Johan Steen

    (@artstorm)

    Recurring donations is not something I’ve considered implementing before. But yes, by passing in a few more parameters to the button, that can done, so technically, no problem.

    It’s not something planned for the upcoming release, but I can consider it for a future one, I wouldn’t dare to give a time estimate though.

    Sweet! I am happy it worked out for you!

    Cheers,
    Johan

    Hi,

    I’d like to point you in the right direction, and as I see it you have two options. If you go with your first snippet of code, you can use post_extract instead of post_content, and use the extract field in the posts for the short version of your testimonial when it’s a long one. And have a condition that checks if a post extract exist, and if not, use post_content as before.

    But going that route, means more work as you have to add content both to the post content and to the post extract when inserting testimonials. In the long run it’s of course quicker and more elegant to just have to insert a read more tag.

    So that’s where your second snippet of code comes into place. What you want is nested loops, as you are already within a loop. WordPress do support multiple loops -> to have a loop within a loop, and you can find some examples here to get you going.

    http://codex.wordpress.org/The_Loop#Multiple_Loops

    Anyway, as your question is more of a general “how to develop something for WordPress”-question than a specific support question for this plugin, you should probably try to ask about nested loops in the more general forums here if you need more code examples / a more elaborate answer how to deal with that.

    I hope this help you though.

    Cheers,
    Johan

    Hi,

    If I remember correctly, for “Read More” to work in WP you need to instruct it where you want the read more link to appear. ie, where to make the break in the post. You can do that by inserting a more tag in your post.
    <!--more-->

    Have you done that? If not, that would be a place to start and see if it shows up.

    Plugin Contributor Johan Steen

    (@artstorm)

    Hi,

    Looking at the html at your link, it seems like you have a modified version of the plugin. You can do a similar modification with the latest version by modifying views/paypal-button.php, and you should be sorted.

    I’ll try to include a filter for the entire form for the next version, so you can do modifications like this, without modifying the plugin source – which will make the modification survive plugin upgrades.

    Cheers,
    Johan

    Plugin Contributor Johan Steen

    (@artstorm)

    This might help you get going, place it in your theme’s function.php file.

    add_filter( 'paypal_donations_purpose_html', 'display_paypal_purpose' );
    
    function display_paypal_purpose( $field )
    {
    	$field = str_replace( 'hidden', 'text', $field );
    	$field = '<label for="item_name">Purpose:</label>'.$field;
    	return $field;
    }

    Cheers,
    Johan

    Plugin Contributor Johan Steen

    (@artstorm)

    Gene, I just modified my reply above, with a code change. As I just realized that new won’t work anymore either when calling the plugin code from outside the plugin. So try the code above now.

    Cheers,
    Johan

    Plugin Contributor Johan Steen

    (@artstorm)

    Hi Gene,

    The class has changed name since v1.7, so it’s now called PayPalDonations() instead of paypal_donations(). And it’s now a Singleton class, so if it’s already been initiated (which it has by the plugin system, it shouldn’t be started with a new)

    If the theme is calling the plugin directly you need to modify the code you posted above slightly. Also the method to generate the shortcode has changed name from paypal_shortcode() to paypalShortcode().

    Modifying your block of code to this, should do the trick for you:

    <?php
        $paypal = PayPalDonations::getInstance();
        $atts='';
        echo $paypal->paypalShortcode($atts);
    ?>

    Cheers,
    Johan

    Plugin Contributor Johan Steen

    (@artstorm)

    Let me know if you have any problems implementing a filter, and I can give you some example code.

    I try to avoid to expose to many of the optional/specialized parameters in the GUI, to keep the plugin as simple to use as possible.

    Plugin Contributor Johan Steen

    (@artstorm)

    1. The update process is outside the control of a plugin and indicates a problem with your server if it is not working.

    If you can’t neither update or delete, it definitely sounds like the permissions on your server is not configured correctly.

    2. The settings are stored in the database, not in the plugin files. So if you manually delete the plugin, it’s impossible for the settings to get lost, so you must have made another user error.

    You need to contact your service provider if you have technical problems or try one of the free plugins with similar functionality if you believe the plugin is the problem.

    Plugin Contributor Johan Steen

    (@artstorm)

    Hi,

    The plugin those not expose those parameters on the frontend. The plugin does allow that behavior to be overriden using a filter though. The purpose is exposed to allow for a change on the frontend. You can hook into that filter and change it to a text box for instance.

    paypal_donations_purpose_html

    I’ll probably add more filters in a future version, but in the current version, using the purpose filter, should get you close to your need anyway.

    Cheers,
    Johan

    Plugin Contributor Johan Steen

    (@artstorm)

    Hi, that looks like a generic server problem with the plugin upgrade process. You should probably just try to download it again.

Viewing 15 replies - 106 through 120 (of 234 total)