Replies
- Tosin on May 11, 2023 at 6:13 pm in reply to: [Resolved] Buddyblog pay per post improvement/suggestion #49457
Thanks for the feedback Brajesh
You got the suggestion right
I want a settings in the product section to also enable users to mark old posts or unpaid posts and expired paid posts as sticky.
So when user edits an old post they can select a product price and promote/feature old unpaid post as sticky
NEW WORKFLOW ON POST EDIT
Clicking the (update) button will now redirect the user to cart or checkout page, after successful payment the post will now be updated and also become stickyNOTE – this new workflow will only take effect if a price option was selected in the pay per post field while updating an old post.
Thanks
Thanks
please note that I changed the button ID from wp-submit to bl-login-submit in my child theme
Alternatively how can I disable all internal recording of notifications in database while leaving the notification component enabled, so now all email notifications settings would be enabled
I want to disable the notification component from the settings but still enable email notifications for the following
ENABLE EMAIL NOTIFICATIONS FOR
1. Private messages
2. Activity – @mentions
3. Activity – A member replies to an update or comment you’ve postedPlease note that I still want users to have access to the email notification settings. I noticed that disabling the notification component would also remove the email notification settings for the 3 items stated above
Gentle reminder
- Tosin on March 30, 2023 at 10:09 pm in reply to: [Resolved] BuddyBlog pay per post – remove post from category on expiration #49039
Thank you Brajesh
this is now resolved
ok thanks Brajesh,
I have disabled it, please kindly let me know if there will ever be a replacement or update for the medium editor.
Hi Brajesh
After further testing I noticed that the encoding issue only occurs when publishing or editing with the buddyblog medium editor.
After deactivating the buddyblog medium editor, everything works fine and there are no more encoding issues.
I just found out its an encoding problem that can occur on old post when database has been migrated,
I tried this code but it did not work
function fix_weird_characters() { global $wpdb; $replacements = array( '“' => '“', 'â€' => '”', '’' => '’', '‘' => '‘', '—' => '–', '–' => '—', '•' => '-', '…' => '…' ); foreach ($replacements as $key => $value) { $query = $wpdb->prepare( "UPDATE {$wpdb->posts} SET post_content = REPLACE(post_content, %s, %s)", $key, $value ); $wpdb->query($query); } } add_action('wp_loaded', 'fix_weird_characters');Thanks Brajesh
Illbe looking forward to the next update