Mayuri

Hello @manek43509

There might be jquery conflict in admin , did you check by F12 on adminside console ?

Open the browser’s Developer Tools (Right-click anywhere on the page > Inspect > go to the Console tab) and check if any JavaScript errors are logged.

Because With my Project WordPress 6.7 it is working perfectly fine .

Thanks

Hello,

Here’s a solution to fix that:

1. Set the locale to Bulgarian: You can use the setlocale() function to ensure that the date is displayed in the correct language.
2. Modify your shortcode function: Update the displayTodaysDate function to set the locale for Bulgarian before generating the date.

Here’s an updated version of your functions.php code:

function displayTodaysDate( $atts )
{
    // Set the locale to Bulgarian (Bulgarian locale may vary depending on your server setup)
    setlocale(LC_TIME, 'bg_BG.UTF-8', 'bg_BG', 'bg', 'bulgarian');

    // Return the date in the desired format
    return strftime('%A, %B %d, %Y');
}
add_shortcode( 'datetoday', 'displayTodaysDate' );

Key points:

1. setlocale(): This function is used to set the current locale. We’re setting it to Bulgarian (bg_BG.UTF-8). The other variants (bg_BG, bg, bulgarian) are used as fallbacks in case one of them isn’t available on the server.
2. strftime(): This function formats the date according to the locale set by setlocale(). It will output the date in Bulgarian. The format '%A, %B %d, %Y' is similar to the format you wanted (l, F j, Y), but it works with strftime().

Things to check:

• Locale availability: Ensure that the Bulgarian locale (bg_BG.UTF-8) is available on your server. If it’s not, you might need to install or enable it on your server, or use a different format that doesn’t depend on setlocale().
• WordPress language settings: Make sure that your WordPress language is set to Bulgarian in Settings > General. This helps ensure that WordPress uses the correct translation for dates, numbers, and other locale-specific data.

With this modification, when you use the [datetoday] shortcode, the date should be displayed in Bulgarian, as long as the correct locale is supported on your server.

Hello

https://prnt.sc/tLp2KI27KMpx , see my wordpress version is 6.7 , there is no problem in Save / Update button when you add new post / Edit an existing post , see screenshot : https://prnt.sc/vXNEPk2xXgVR

https://prnt.sc/c0S8Rj-Cmi6t

So WordPress 6.7 has no problem , there should bee some script / code in your theme / plugin of your project which might be causing conflict .

Did you try with fresh wordpress 6.7 installation ?

• This reply was modified 2 days, 1 hour ago by Mayuri.

Hello @aminulxpeed

There are 2 ways but Be cautious.

1. Change WordPress Username via PHPMyAdmin (Direct Database Edit)

You can also change your username directly in the WordPress database using PHPMyAdmin. Here’s how:

1. Log in to your web hosting control panel (like cPanel).
2. Open PHPMyAdmin (found under “Databases”).
3. Select the WordPress database for your site.
4. Find and open the wp_users table.
5. Locate your current username in the table and click Edit.
6. Change the user_login field to the desired username.
7. Click Go to save the changes.

Important: Be cautious when editing the database directly. It’s always a good idea to back up your database before making any changes.

2.

Change WordPress Username Programmatically with PHP Code

You can use a custom PHP script to change the username programmatically, but this would involve direct manipulation of the WordPress user table. Here’s an example of how you could do it:

PHP Code Example:

function change_wordpress_username($user_id, $new_username) {
    global $wpdb;

    // Check if the new username is unique
    if( username_exists( $new_username ) ) {
        return false; // Username already exists
    }

    // Update the user login name
    $wpdb->update(
        $wpdb->users,
        array( 'user_login' => $new_username ), // Data to update
        array( 'ID' => $user_id ), // Which row to update
        array( '%s' ), // Data format
        array( '%d' ) // Where clause format
    );

    // Optionally, update the display_name as well
    $wpdb->update(
        $wpdb->users,
        array( 'display_name' => $new_username ), // Update display name
        array( 'ID' => $user_id ) // Which row to update
    );

    return true;
}

// Usage: Change username of user with ID 1 to 'new_username'
change_wordpress_username(1, 'new_username');

Make sure to Pass User ID relevant to your username for above code , i have used user id 1 only for example , you can replace with yours .

This function updates the user_login field in the wp_users table (which is the WordPress username) to the new one. You can run this code in your theme’s functions.php file or as a custom plugin.

Note: Be sure to remove or comment out the code after it has run, as you wouldn’t want it executing every time your site loads.Important Notes:

• Permissions: Only an administrator can change the username via PHP, so make sure you’re logged in as an admin.
• Repercussions: Changing the username can affect login credentials and could potentially break links or references to the old username in the database.
• Security: Be careful when running custom PHP scripts on your live site. Always backup your site and database before making changes.

Hello @sherweb

It sounds like you’re describing an issue where excessive white space appears above the header when you scroll up, and then it “bounces back” when the scrolling action stops. This kind of behavior is often related to the layout and styling of a website, and it can be caused by a few different factors. Let’s break down the potential causes:

1. Browser-Specific Rendering Issues

• Opera vs. Firefox: Browsers can sometimes handle layout and rendering slightly differently, especially with newer web technologies like Flexbox or Grid, or CSS properties like scroll-behavior. If the issue is more pronounced in Opera than Firefox, it’s possible that Opera is struggling to render the layout correctly, either due to browser quirks or specific CSS styles that aren’t well-supported or are interpreted differently.
• Solution: You could try updating both browsers to the latest versions or test with other browsers (like Chrome or Edge) to see if the issue persists across more than one browser. You can also try running your site through browser compatibility tools like Can I Use to check for any compatibility problems.

2. Sticky Header or Positioning Issues

• If your site uses a sticky header (or a fixed position for the header), sometimes the behavior you’re describing happens when there are CSS issues related to position: sticky; or position: fixed;. If the page has extra space when scrolling back up, it could be due to the header not behaving correctly with other content or with the scroll position.
• Solution: Check the CSS for the header. If you’re using position: sticky; or position: fixed;, try adjusting the top value, or use z-index to ensure it sits on top of other content properly. Also, try ensuring that the parent container of the header has enough space to accommodate it.

3. JavaScript or Scroll Behavior

• Some modern sites use JavaScript to add dynamic scroll effects (e.g., parallax, smooth scrolling, etc.). These effects can sometimes lead to issues like bouncing when the scroll position changes unexpectedly, especially if the script isn’t properly managing the scroll events.
• Solution: Check if there’s any JavaScript code that’s altering the scroll behavior, and ensure that it’s implemented correctly. You might want to test the site without JavaScript to see if the issue persists.

4. Overflow or Margin Collapse Issues

• This issue can also arise from CSS overflow or margin collapse. For example, if the page layout is set to overflow: hidden; or a combination of margin and padding properties is used improperly, the browser might show unexpected spaces when you scroll.
• Solution: Double-check the CSS for any overflow properties applied to the body, html, or wrapper elements. Try setting overflow: auto; or overflow-x: hidden; where appropriate.

5. Viewport or Media Query Breakpoints

• Sometimes, the issue is related to how the site scales across different screen sizes or when specific media queries activate (for example, when you change the window size or the site adjusts to mobile view). In some cases, there could be an unintended effect where white space appears because the layout isn’t adjusting correctly.
• Solution: Check your media queries to ensure that your site layout behaves as expected across different screen sizes. Inspect the page on smaller screens to see if the issue occurs in those cases.

6. CSS Scroll Snapping

• If you’re using CSS Scroll Snap (a feature that controls the scrolling behavior to snap to certain positions), it could cause the page to “bounce” back when scrolling. This is more noticeable in some browsers and may give the appearance of extra white space.
• Solution: Check if you’re using scroll-snap-type or scroll-snap-align properties and adjust or remove them if necessary to see if the behavior changes.

Hello @caritatang

The error message you’re encountering is related to a translation issue in the Astra theme (or potentially a plugin) on your WordPress site. The error is caused by the _load_textdomain_just_in_time function being triggered too early during the page load, which is causing issues with the WordPress headers and the login page. This type of issue often arises after a WordPress or plugin update.

Here’s how you can resolve the issue:

1. Temporarily Disable All Plugins and Themes (via FTP or File Manager)

Since you can’t access the WordPress login page due to this error, you’ll need to disable your plugins and/or theme temporarily. The most common cause of this issue is a conflict with a plugin or theme (in your case, likely the Astra theme, but it could also be a plugin). Here’s how to do that:A. Disable Plugins

1. Access your website files:
   • Use FTP or File Manager (via cPanel or your hosting provider) to access the WordPress files.
2. Navigate to the wp-content folder:
   • Go to wp-content > plugins.
3. Rename the plugins folder to something like plugins_old. This will deactivate all plugins on your site.
4. Try to access your login page:
   • After renaming the folder, try to access the WordPress login page again (yourdomain.com/wp-login.php). If you’re able to log in, the issue is most likely with one of your plugins.
5. Reactivate plugins one by one:
   • Rename the plugins_old folder back to plugins and go into the folder. Then, rename each plugin folder back to its original name one at a time and check your site after each reactivation. This will help you identify which plugin is causing the issue.

B. Disable the Astra Theme

If the problem persists after deactivating plugins, it could be related to the theme. To test this, you can deactivate your current theme (Astra in your case) by following these steps:

1. Access the wp-content/themes folder.
2. Rename the Astra theme folder to something like astra_old.
3. WordPress will now default to the default theme (usually Twenty Twenty-One or similar). Try logging in again.

If the issue is resolved after renaming the theme, the problem is with the Astra theme, which might need an update or fix.

2. Manually Fix the Translation Issue in the Astra Theme

The error suggests that the translation for the Astra theme is being loaded too early. You can try fixing this by adding a small fix to the theme’s functions file, but only do this if you’re comfortable with PHP.

1. Access the theme’s functions.php file:
   • Go to wp-content/themes/your-active-theme/functions.php.
2. Look for any translation-related code:
   • Check if there’s any code related to loading translations for the Astra theme. It might look like this:

load_theme_textdomain('astra', get_template_directory() . '/languages');

Change the code to load translations at the correct time:

• The translation should be loaded during the init action. If the code isn’t already wrapped in the init action hook, you can modify it like this:

add_action('init', function() {
    load_theme_textdomain('astra', get_template_directory() . '/languages');
});

Save the file and check your site again.

Hello

Using Clover’s Payment Links + WooCommerce Donation Product

What you need: You can create a simple donation form using a WooCommerce product (e.g., “Donation”) and use Clover’s Payment Links to accept payments.

Steps:

1. Create a Donation Product in WooCommerce:
   • Go to your WordPress dashboard.
   • Create a simple WooCommerce product called “Donation”.
   • Set the price to 0 or a minimum amount, depending on how you want to handle pricing (since Clover Payment Links will handle the actual payment).
2. Install and Configure the “Product Add-Ons” Plugin (Free):
   • You can use the free version of WooCommerce Product Add-Ons plugin to add extra fields for the user to select preset donation amounts (e.g., $25, $50, $100).
   • You can allow a custom donation by enabling a text input field where the user can enter any amount.
   • Install the free version of Product Add-Ons:
     • WooCommerce Product Add-Ons (Free)
     • This version lets you add checkboxes, radio buttons, and text fields to allow users to select or input custom amounts.
3. Create a Payment Link in Clover:
   • Log in to your Clover Dashboard.
   • Use Clover’s Payment Links feature to generate a unique link for your donation product.
   • Go to Payments > Payment Links and create a payment link for the amounts you want to accept (e.g., $25, $50, etc.). Clover will generate a unique URL for each amount.
4. Link Payment Options:
   • On your WooCommerce donation product page, link the preset donation options (e.g., $25, $50) to the corresponding Clover Payment Links.
   • You can manually set these up in the Product Add-Ons section, where each option would lead the user to the relevant Clover Payment Link (e.g., a button that redirects to a Clover Payment Link for $25 donation).
   • Users will click the payment link for the preset amount they wish to donate, and Clover will process the payment.

You can try below plugins also :

1. https://www.ads-software.com/plugins/wpc-name-your-price/
2. https://www.ads-software.com/plugins/charitable/
3. https://www.ads-software.com/plugins/woo-custom-product-addons/

Hello

1. Clear Browser Cache and Disable Extensions

Sometimes, the issue could be due to browser cache or conflicting extensions:

• Clear your browser cache: This ensures you’re loading the most recent scripts and styles.
• Disable browser extensions: Extensions (like ad blockers, or privacy-related extensions) can sometimes interfere with the WordPress editor. Try disabling them or open the site in Incognito mode to rule out this issue.

2. Check for JavaScript Errors

The disappearing buttons could be related to JavaScript errors that are blocking the UI from rendering correctly.

• Open the browser’s developer tools:
  • In Chrome or Firefox, right-click anywhere on the page and select Inspect (or press Ctrl+Shift+I).
  • Go to the Console tab to check for any JavaScript errors that may be occurring.
  • If you see any errors, these might provide a clue as to what’s causing the issue. Common causes can be conflicts with plugins, themes, or scripts.

3. Deactivate All Plugins and Check Again

Plugin conflicts are a common culprit when WordPress behavior changes after an update.

1. Deactivate all plugins:
   • Go to Dashboard > Plugins > Installed Plugins.
   • Deactivate all plugins.
2. Check if the Update buttons reappear:
   • Try updating a page while all plugins are deactivated. If the buttons are visible again, the issue is likely with one of the plugins.
3. Reactivate plugins one by one:
   • Reactivate plugins one at a time and check if the buttons disappear after reactivating a specific plugin.
   • This will help you isolate the plugin causing the issue.

4. Switch to a Default Theme

The problem could also be related to your theme. Some themes might not be fully compatible with the latest version of WordPress or could have custom scripts that interfere with the editor.

1. Switch to a default theme like Twenty Twenty-Three or Twenty Twenty-Two.
   • Go to Appearance > Themes and activate a default WordPress theme.
2. Test the editor:
   • After switching to the default theme, check if the Update/Save buttons appear.
   • If the problem resolves, the issue is likely with your theme. In that case, you may need to update your theme or contact the theme developer for support.

5. Check for JavaScript or CSS Conflict with Custom Code

If your site has custom JavaScript or CSS (added via theme options, a child theme, or a custom plugin), there may be a conflict causing the buttons to disappear.

1. Temporarily remove or comment out any custom JavaScript or CSS.
   • If you’re using a child theme, try disabling custom scripts/styles in your theme’s functions.php file or custom CSS in the theme options.
2. Check the editor again after removing custom code to see if the problem resolves.

6. Check WordPress Core Files

If a core WordPress file was corrupted or failed to update properly, that might cause issues with the editor interface.

1. Reinstall WordPress:
   • Go to Dashboard > Updates.
   • Click Reinstall Now to reinstall the core WordPress files without affecting your content or settings.
   • This can fix any issues with missing or corrupt files that may have occurred during the update.

7. Check for Console or Network Errors (Advanced)

If you’re still facing issues, you can perform a deeper diagnostic check:

1. Network Tab:
   • In your browser’s developer tools, go to the Network tab.
   • Refresh the page and look for failed network requests (marked in red). These requests might indicate problems with assets (JavaScript, CSS, AJAX requests) that are not loading properly.
2. Console Tab:
   • Look for JavaScript errors that could be affecting the WordPress editor’s functionality.

Hello ,

A staging site allows you to make and test changes, updates, and other customizations before pushing them to your live website, which helps mitigate the risk of breaking functionality or causing issues on the live site.

1. Create a Staging Site (Duplicate of Live Site)

There are a few ways you can create a staging site:Option 1: Using a Staging Plugin (Easy & Fast)

Several plugins can help you duplicate your live site and create a staging site with minimal effort:

• WP Staging: This plugin allows you to create a copy of your website and set up a staging site on the same server or subdomain.
• Duplicator: This plugin can clone your site and move it to a different location, allowing you to create a staging site with a different name.
• UpdraftPlus Premium: This plugin offers a staging feature that can help you duplicate your site with a click of a button.Steps using WP Staging (as an example):
  1. Install the plugin: Go to Plugins > Add New and search for WP Staging. Install and activate it.
  2. Once installed, go to WP Staging > Staging Sites in your WordPress admin dashboard.
  3. Click Create New Staging Site.
  4. The plugin will create a copy of your site, including all files and the database, and allow you to access it on a subfolder or subdomain.
  5. After the staging site is created, you can log into it and begin testing changes.

Option 2: Manual Duplication via cPanel

If you prefer a more manual approach or your hosting provider doesn’t support staging plugins, you can manually create a staging environment:

1. Create a Subdomain: In your hosting account (via cPanel or another control panel), create a subdomain (e.g., staging.yoursite.com).
2. Copy Files: Copy all files from your live site to the subdomain directory (either via FTP or using the cPanel File Manager).
3. Duplicate the Database: Create a new database and user for your staging site. Then, export your live site’s database (via phpMyAdmin) and import it into the new database.
4. Edit wp-config.php: In the staging site’s wp-config.php file, update the database name, username, and password to match the new staging database.
5. Adjust Site URLs: The staging site will still point to your live site’s URLs, so you need to update the site URL settings for the staging site. You can either:
   • Use phpMyAdmin to edit the wp_options table (siteurl and home).
   • Or, add these lines to wp-config.php for the staging site:

define('WP_HOME', 'https://staging.yoursite.com');
define('WP_SITEURL', 'https://staging.yoursite.com');

Disable Search Engine Indexing: To prevent search engines from indexing your staging site, go to Settings > Reading in the staging site’s dashboard and check the box for “Discourage search engines from indexing this site”.

Hello @markone21

Override Sorting Order with Custom Code
Add this code to your theme’s functions.php file (preferably in a child theme):

function custom_woocommerce_product_query( $q ) {
    // Check if we're on a product archive page
    if ( is_product_category() || is_shop() ) {
        $q->set( 'orderby', 'date' ); // Sort by date
        $q->set( 'order', 'DESC' ); // Newest first
    }
}
add_action( 'woocommerce_product_query', 'custom_woocommerce_product_query' );

This code ensures that the query fetching products is ordered by date in descending order, which will display the newest products first.

Hello ,

You could add this code to your theme’s functions.php file to display random products at the checkout:

function display_random_products_at_checkout() {
    // Fetch random products
    $args = array(
        'posts_per_page' => 5,
        'post_type' => 'product',
        'orderby' => 'rand', // Random order
        'post_status' => 'publish',
    );
    $random_products = new WP_Query($args);

    if ($random_products->have_posts()) {
        echo '<h3>Special Offers Just For You</h3>';
        echo '<ul>';
        while ($random_products->have_posts()) : $random_products->the_post();
            global $product;
            echo '<li><a href="' . get_permalink() . '">' . get_the_title() . '</a> - ' . wc_price($product->get_price()) . '</li>';
        endwhile;
        echo '</ul>';
    }
}
add_action('woocommerce_review_order_before_payment', 'display_random_products_at_checkout');

While there is no single plugin that combines all your needs out of the box, you can achieve your goal by combining the right plugins (like CartHook, One Click Upsell, or Dynamic Pricing) with a bit of custom coding to handle the random product selection. Additionally, using a WooCommerce checkout customization plugin or even building a custom solution would give you the flexibility you need to create a fully dynamic checkout experience.

Hello @richie181

To Disable Debugging:

1. Edit the wp-config.php file: Access the file via FTP or your hosting file manager, and add or update the following lines of code (if not already present):

define('WP_DEBUG', false);
define('WP_DEBUG_LOG', false);
define('WP_DEBUG_DISPLAY', false);

WP_DEBUG: When set to false, this turns off debugging mode.

WP_DEBUG_LOG: If you don’t want to log errors to a file (usually found in the wp-content folder), set this to false.

WP_DEBUG_DISPLAY: This controls whether errors are shown on the front end. Setting it to false prevents errors from being visible to site visitors.

Save the file and upload it back to the server (if you’re using FTP).

Try a Clean Install on a Staging Site

If none of the above works, try testing on a staging site with a fresh WordPress install:

• Install WordPress fresh on a staging site.
• Activate only the default theme (Twenty Twenty-Three).
• Install only essential plugins (leave out any non-essential ones).
• Test creating and editing posts as Editor/Author.

This can help confirm whether the issue is related to your existing theme, plugins, or server configuration

Hello @ayaanglobals

1. Check the Sitemap for Unauthorized Content

It seems the sitemap has been compromised. The sitemap should be found in the following locations (depending on the plugin you’re using):

• If you’re using Yoast SEO, it’s usually located at:

https://yourdomain.com/sitemap_index.xml

If you’re using RankMath, it would be at:

https://yourdomain.com/sitemap_index.xml

If you’re using Google XML Sitemaps:

https://yourdomain.com/sitemap.xml

If the sitemap is showing unauthorized content, you can manually check the content of your sitemap (in your browser or by opening the XML file) to see if there are any rogue URLs or posts that you don’t recognize.Action:

• If you find any unauthorized URLs, remove them manually. If your sitemap is being generated by a plugin (like Yoast or RankMath), regenerate the sitemap after cleaning it.
• If you’re unable to access the sitemap through the regular URLs, the attacker might have hidden the file or changed its location. You can check the robots.txt file to see if the sitemap is still referenced

2. Scan for Malware or Suspicious Code

Hackers often inject malicious code into themes, plugins, or WordPress files, which could also explain changes to your sitemap or other parts of the site.Action:

• Use a Security Plugin: Install a reputable WordPress security plugin such as:
  • Wordfence Security: It scans your website for malware, backdoors, and other vulnerabilities.
  • Sucuri Security: It offers a website scanner that checks for malware, and their paid service can help clean up your site.
  • iThemes Security: Another great security plugin for scanning and hardening your website against further attacks.
  Run a full scan with the plugin and follow the instructions provided to remove any malicious code.
• Check WordPress Files:
  • Check the wp-content folder, especially the themes and plugins directories, for any unauthorized files.
  • Look for suspicious files, especially those with obfuscated or encoded content, such as files with random names or .php files in the uploads directory.

3.Reinstall Core Files, Themes, and Plugins

It’s possible that the hacker modified core WordPress files, your theme, or plugins. Reinstalling these can help remove any malicious code that has been added.Action:

• Reinstall WordPress Core: Go to Dashboard > Updates in the WordPress admin and click Reinstall Now to reinstall the core WordPress files without affecting your posts or media.
• Reinstall Themes and Plugins: For any active themes or plugins that seem suspicious, you can delete them and reinstall the latest versions from trusted sources (e.g., the official WordPress repository or a reputable vendor). If you’re using custom or third-party plugins, ensure you download the latest, unmodified version from a trusted source.

4. Change Passwords and Secure Your Site

Once you’ve cleaned up the site, it’s essential to change all user passwords and tighten security to prevent future compromises.Action:

• Change Your Admin Password: Log in to the WordPress admin and change your password immediately, using a strong password (avoid common words or simple patterns).
• Update Database Password: Change the database password from your hosting control panel (cPanel or similar). Then, update the wp-config.php file with the new database password.
• Enable Two-Factor Authentication: Use a plugin like Google Authenticator or Wordfence to enable two-factor authentication (2FA) for your WordPress admin accounts.
• Limit Login Attempts: Use a plugin like Limit Login Attempts Reloaded to limit login attempts and prevent brute-force attacks.

Hello @igorfelluga

Here are some options that could work for your use case

1. Amelia – Appointment Booking Plugin

Amelia is a robust WordPress appointment booking and scheduling plugin. It’s designed for businesses like salons, clinics, and other service-based companies, but it can be extended to integrate with external APIs if needed.

• Features:
  • API Access: Amelia has a built-in API that can be used to create and manage appointments.
  • Customizable: You can integrate Amelia with your Angular app by using the API to fetch and display appointments from the external system.
  • Multiple Views: Amelia supports a calendar view, booking forms, employee management, and notifications.
  • Booking & Payments: You can customize the booking form and integrate payments.

2. Bookly – Appointment Booking Plugin

Bookly is a popular, feature-rich booking plugin for WordPress. It’s a premium plugin, but it offers extensive customization and API access.

• Features:
  • Frontend Booking: Customers can book appointments directly through a frontend interface.
  • API Access: Bookly has a REST API that you can use to integrate external appointment data, similar to your Angular calendar.
  • Customizable: It offers an interface that you can customize to fit your needs, and you can use it to sync appointments from external APIs.
  • Payment Integration: Bookly supports various payment gateways for booking services.

3. WP Simple Booking Calendar

WP Simple Booking Calendar is a lightweight plugin that provides a basic calendar for managing bookings and appointments. It’s simpler compared to the other plugins but could be a good fit if you want a quick solution with the ability to fetch appointments via an API.

• Features:
  • Simple booking calendar with availability management.
  • Frontend view for customers to check available dates.
  • Basic booking functionality, which you can extend via custom code.

4. EventON – Event Calendar Plugin

EventON is a premium calendar plugin that allows for event and appointment scheduling. While primarily designed for events, it can be adapted to manage appointments as well, and it’s flexible enough for API integration.

• Features:
  • Beautiful calendar layouts (monthly, weekly, daily views).
  • Support for recurring events and appointments.
  • Customizable event metadata fields for extra appointment details.
  • API integration through custom code (REST API).

5. BirchPress – Appointment Booking Plugin

BirchPress is another excellent option for booking and scheduling appointments. It’s designed for service-based businesses and supports a range of features like appointment reminders, payments, and custom booking forms.

• Features:
  • Front-end booking system with customizable appointment forms.
  • Calendar views for service availability.
  • Payment integrations with PayPal, Stripe, etc.
  • API Access for managing appointments.