wadehammes

To add to this, I am seeing an error/warning in /var/www/html/wp-content/plugins/speed-booster-pack/includes/classes/class-sbp-js-optimizer.php regarding an offset of 5 being undefined/null.

@krsh333 I was able to update the plugin myself to achieve exporting the description. If you feel comfortable touching PHP code, here is how you can export and import description:

in includes/exporter/data/data-wf-post-columns.php, add the following to the end of the $columns array before the closing );:

'user_description' => 'user_description',
(add a comma after ‘roles’)

in includes/importer/data/data-wf-reserved-fields-pair.php add the following to the end of the $columns array before the closing );:

'user_description' => 'user_description | user_description',
(add a comma after ‘roles’)

in includes/importer/class-wf-csv-parser.php, add the following to the end of the $this->user_base_fields array before the closing );:

'user_description' => 'user_description',
(add a comma after ‘roles’)

in includes/importer/class-wf-customerimpexpcsv-customer-import.php, add the following after line 618:

$user_description = (!empty($data['user_details']['user_description'])) ? $data['user_details']['user_description'] : '';

and in the same file, in the wp_update_user array on line 625, add the following to the end of the array:

'description' => $user_description,
(add a comma after ‘user_status’)

Very simple update to include a field that should be supported in the basic version of this plugin. Hopefully they will add it in a future version, but I was on a tight deadline and needed it now.

I also would like to know if user_description is exportable or not, it is pretty imperative for a site I am transitioning that has 300+ users.

• This reply was modified 5 years, 1 month ago by wadehammes.

Ah nice! Cool (might make sense to add the UI difference there in the explanation), I would have never guessed that.

The shortcode works for me, but the function is returning an empty array:

$taxonomies = array('project_categories', 'service_categories');
$has_related = km_rpbt_related_posts_by_taxonomy($post->ID, $taxonomies);

a var_dump of the function gives me:

array(0) {}

Any thoughts?

—-

I needed to pass the correct post type in the args. Nevermind ??

• This reply was modified 6 years, 8 months ago by wadehammes.
• This reply was modified 6 years, 8 months ago by wadehammes.

Any timetable for this? Nevermind, the issue link is working now.

• This reply was modified 6 years, 12 months ago by wadehammes.

Awesome! Thank you for considering, and for the awesome plugin.

Hm, I don’t think deactivating the plugin is a good solution. I’ve tried deregistering the lazy load script if is_amp_endpoint() returns true, but doesn’t work. Would like to see this fixed.

• This reply was modified 7 years, 9 months ago by wadehammes.

Same here, same error. 500’d my site, had to go into the server and rm -rf the-events-calendar plugin to get it back.

Where can I get older releases?

Closing this out as it will be resolved.

Angelo – awesome, works for me! I can wait until the next release. Thanks for the great product btw!

Also, thanks for the help too, Shawn, sorry I was being unclear — hectic day at work!

For better context, here is the Web Page Test for my homepage, which has NO powerpress functions at all, yet the mediaelement.js and player.min.js are loaded to the page (click the waterfall to view it).

https://www.webpagetest.org/result/150915_D6_13KA/

This is unnecessary and should be resolved.

I think you are misunderstanding the issue. There is no problem with the players or the mediaelement. Everything works fine. I just do not want the scripts loading on pages where there is now powerpress because that is three unnecessary HTTP requests.

Shawn – yes. The scripts for the players and media element still appear on pages where there is no powerpress shortcode or snippet. I think the way the plugin is set up it just enqueues the scripts on all pages no matter what.

I figured it out, i had replaced the overall blog index.php with the actual theme index.php.

Surprised it all still worked with that.