Milan Dinić
Forum Replies Created
-
Thanks for report. This is added in version 3.1.
This is finally added in version 3.1. Please report any issues.
I don’t know. Try with your admin or look for help on Google, I didn’t experience this error.
Sorry for late reply. This is caused by setting on your server since I get this error in Javascript debugger:
XMLHttpRequest cannot load http://artiss.co.uk/sandbox/wp-content/plugins/gravatar-signup-encouragement/gravatar-check.php. Origin http://www.artiss.co.uk is not allowed by Access-Control-Allow-Origin.Great! Thank you for fast response.
Patch is used with SVN. SVN is used by plugin authors to submit code changes to WordPress plugins repository.
So this patch is intended for MattyRob who should merge it with plugin’s source code. If he doesn’t accept this feature, I’ll then publish how to enable it.
I’ve created a patch that enables one-click subscribing/unsubscribing for registered users. More details on Trac ticket.
@elarson I agree with second thing about easier way for registered users to unsubscribe. Currently its very confusing even for advanced users, not to mention ones that are not tech savvy.
I have some code that makes workaround without changing way Subscribe2 works under the hood which makes one checkbox for subscribing/unsubcribing and I’ll propose importing it to the core.
However, I don’t agree with first thing you mention. When user is deleted, it’s not Subscribe2’s business to subscribe that user as a public user. That is a job of administrator to do, either manually or via custom code.
Thanks for this report and a patch.
I actually thought about adding this since I got similar reports (for non existing gravatar it doesn’t report) and I created a test plugin but there wasn’t any feedback so I forgot about it.
There is one thing that I would change from your patch. Instead of cURL I would use WordPress HTTP API which is the only right way to use this kind of stuff in WordPress.
You may wondering why I didn’t use it instead of get_headers. Reason is that WordPress is much slower and here we need result very fast.
So WordPress should be used as a fallback as in your example.
I will add this but I need to test it some time and I think that it’s not crucial to have it fixed immediately (you already have temporary solution for yourself).
I believe that this issue is solved in version 3.0.
Forum: Installing WordPress
In reply to: WordPress.com blog transferred to .org – content disappearedLook at those links below:
http://en.support.wordpress.com/export/
http://wordpress.org/extend/plugins/wordpress-importer/Forum: Plugins
In reply to: [Grunion Contact Form] [Plugin: Grunion Contact Form] Not i18n FriendlySure, here it is.
Note that files should be placed in folder languages, and that I created POT file manually but you should put one inside folder for other translators.
How about this?
<?php $custom_field_email_address = get_post_meta($post->ID, 'custom_field_email_address', true); echo do_shortcode( '[contact-form to="' . $custom_field_email_address . '"]' ); ?>Forum: Plugins
In reply to: [Grunion Contact Form] [Plugin: Grunion Contact Form] Not i18n FriendlyGreat! I made another patch that fixes one typo and removes two unnecessary lines.
I tested with translation turned on and didn’t find any issues related to this changes. There is only a minor thing with
_nx_noop()that I already mentioned in ticket when I created a first patch.I just found a different issue related to i18n: if you create a form with non Latin characters and then go again to Grunion’s screen for that post, preview of a form is sort of broken because of decoding in
grunion_ajax_shortcode_to_json().If you plan to include translations in a plugin, I can send you mine since I already made it because of testing.
You can put whole Grunion’s shortcode or even put several different shortcodes. What this function does is searching for any shortcode in text that is passed to it.
It’s actually used in core for post content. See documentation.