CodeBard

No problem.

The patronage pipe was intended to be used instead of the current profile link that the plugin sends to, however at the time of the creation of the plugin there wasnt a reliable way to acquire the patronage pipe from Patreon (from their api). This is due to the patronage pipe requiring a user id, which is not possible to automatically acquire the id number without having users log in through patreon or other means.

This feature may be possible with the integration of login with Patreon feature into the plugin. Which is planned for future.

i conclude that you solved this problem based on given information. closing.

Widget behavior is as follows:

If author widget is enabled and on a single post page, author widget shows up if the author has any patreon profile link saved in their profile in wordpress.

If any of them is not true and site widget is added, site widget would show up.

In front page only site widget would show up.

Possibly you were able to find the button. Im closing this ticket. Have a nice day.

The issue persists. I use the wp super cache preloading on 3 sites with 36,000, 14,000, 8000 posts in order, and in every site when a new post or update is done all preloaded files are being cleared. This is without setting the setting ‘clear all cache files when a post is made/updated’.

This makes preload unusable.

I replied to your email, antoinette, but apparently your email provider filters a lot of email, mistaking them for spam.

As i told in there, currently there isnt an option to change the patreon button image, but for now you can do it by replacing the image used directly:

The image is at:

https://yoursite.com/wp-content/plugins/patron-button-and-widgets-by-codebard/images/patreon-medium-button.png

If you overwrite this image with another, that image would be used. You can do this via ftp.

Just try to make sure that you wont use an image that is larger than ~200px, so it will fit widgets and whatnot.

I have modified src/modules/taxonomy.php to have it put into sitemap all the taxonomies regardless of post counts.

However, naturally, this is a modification which will go away next time we update the plugin.

We need a more reliable and permanent way of doing that – through hooks, actions or modules. An option in settings would be much more appreciated.

my pleasure.

Seems to be a PHP version issue. array_replace_recursive is available from 5.3.0. You should check out your PHP version.

https://php.net/manual/en/function.array-replace-recursive.php

Currently no. But if you grab the button by filtering its function, and then assigning its content to a variable, you can later echo that content (button) anywhere.

Did it work then?

Could it be the plugin adds the field AFTER my theme functions.php executes?

Could it be not working because I’m using a child theme?

It’s possible that if the field is being rendered in admin side (user profile editing field in user profile) then theme functions.php may not be getting affected, OR, the plugin is loading after the theme functions.php comes.

A good bet could be to add through your own dummy plugin and having the plugin initialize very late.

Plugin uses ordinary wordpress actions and filters to add that field. Showing the field happens with the below hook operations:

add_action( ‘show_user_profile’, array(&$this, ‘add_custom_user_field’) );
add_action( ‘edit_user_profile’, array(&$this, ‘add_custom_user_field’) );

Then, try removing them first in your theme functions.php :

remove_action( ‘show_user_profile’, array( &$cb_p6, ‘add_custom_user_field’ ) );
remove_action( ‘edit_user_profile’, array( &$cb_p6, ‘add_custom_user_field’ ) );

And adding them with priority:

add_action( ‘show_user_profile’, array(&$cb_p6, ‘add_custom_user_field’),5);
add_action( ‘edit_user_profile’, array(&$cb_p6, ‘add_custom_user_field’,5) );

Modify the number 5 according to where you want the field to appear.

These 4 lines should be placed one after another like this.

ETA is uncertain yet – the new plugin core will be used for many other plugins, hence it necessitates careful development. But it can also be ready rapidly as well. Naturally, we are not talking about a year or so, but months.