borkenkaefer

Sorry for the double post. See: https://www.ads-software.com/support/topic/php-fatal-error-uncaught-error-call-to-undefined-method-wpdbparse_db_host/

Thank you for your answer and your suggestions.

a) is not an option and debians wordpress packages also includes security fixes, so no reason to upgrade for the moment. I probably will stick with b) for the moment or maybe I’ll create my own parse_db_host().

Please adapt the required wordpress version on https://www.ads-software.com/plugins/mailpoet/ and for the future, please specify such changes in the changelog.

@mailpoet, this is still not fixed in 3.16.3 or am I the only one experiencing that problem?

Now with version 3.14.0 it is working again, but I had to fix editor.html because of a TypeError: $ is not a function error.

Replace line 402 in mailpoet/view/newsletter/editor.html:

var $wrapper = $('<span></span>');

with

var $wrapper = jQuery('<span></span>');

to fix it.

• This reply was modified 6 years ago by borkenkaefer.

Hi @wysija,

Yes, I tried with the TwentySixteen and TwentyFifteen themes.

Cache is cleared.

It’s a wordpress on debian and using the wordpress from the package manager (Version 4.7.5). There, all the custom plugins have to be installed under /var/lib/wordpress/wp-content/plugins while the default wordpress installation is under /usr/share/wordpress/wp-content …

If I put the plugin the non debian way unter /usr/share/wordpress/wp-content/plugins/ and do a symlink of the mailpoet to /var/lib/wordpress/wp-content/plugins/ it seems to work.

But this is somehow strange, because all the other plugins I’m using don’t have this problem and it worked normally with version 3.12.0, so I think, something is borked with the paths or calculation of paths in the newer mailpoet versions …

+1, I got the same problem.

@mbrsolution, I’m still cleaning up the code and making it more or less compliant to the WordPress Coding Standard (https://make.www.ads-software.com/core/handbook/best-practices/coding-standards/)

I’ll post here, when it’s ready for the public.

I think I fixed this with following pull request: https://github.com/Sladix/Restrict-Taxonomies/pull/6

Hmm, tried to fix myself. Please have a look. Not tested if everything is working (especially frontend).

https://github.com/Sladix/Restrict-Taxonomies/pull/5

bump!

Maybe it’s the same bug as https://www.ads-software.com/support/topic/category-filtering-broken

I think you’d have to adapt the posts_query query somehow …

Check this out: https://github.com/Sladix/Restrict-Taxonomies/pull/4

Hey,

I added two hooks for my purpose.

First, there is do_action('pre_acui_import_single_user', $headers, $data ); around line 120 in importer.php. I have a column named “categories” of which I create new terms of a certain category.

Second, there is do_action( ‘after_acui_import_users’ ); around line 365 in importer.php. I need this to create an array out of a string with multiple comma separated values.

You’ll find the adaptions in my github repo. I added an example hooks.php file, too. See https://github.com/brknkfr/import-users-from-csv-with-meta

Another thought: Maybe importer.php could check, if $data[$i] value (around line 243) contains a comma separated string, then split it up and turn it into an array … Just a thought.

Yet another thought: It would be nice, as a developer, to have a action hook just after checking if there is any data to manipulate data before saving/updating it. For example for preparing a given CSV file with correct column titles.

And BTW: I just donated a small amount. ??

Nevermind … I mixed up with the permissions of the affected user role which had the manage_categories capability.