Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'wordpress'

Viewing 25 results - 451 through 475 (of 22,644 total)
  • Author
    Search Results
  • #332358
    Guddu Kumar
    Participant

    Yes, it is possible to create a cricket scoring web application using WordPress. While WordPress is traditionally used for content management and blogging, it can be extended to build various types of web applications, including a cricket scoring application.

    Here are the steps you can take to create a basic cricket scoring web application on WordPress:

    1. Choose a WordPress Theme:
    – Select a WordPress theme that suits your requirements or use a sports-oriented theme. There are many themes available that can be customized to fit the design and functionality you need.

    2. Install and Configure WordPress:
    – Set up WordPress on your server and configure it according to your needs. You can use popular hosting providers like Bluehost, SiteGround, or others to host your WordPress site.

    3. Install Relevant Plugins:
    – Use WordPress plugins to add specific functionality to your site. For a cricket scoring application, you might need plugins that handle sports scoring or booking systems. Some popular WordPress plugins for sports include SportsPress, Team Rosters, and Booking Calendar.

    4. Customize and Design:
    – Customize the appearance of your site using the WordPress Customizer or a page builder plugin. Ensure that the design aligns with the branding and requirements of the cricket ground owner.

    5. Implement Cricket Scoring Features:
    – Depending on the complexity of the scoring system you want, you may need to customize or extend existing plugins or develop custom features. This may involve custom post types, taxonomies, and fields to handle match details, scores, and other relevant information.

    6. Ground Availability:
    – Implement a booking or reservation system to display the availability of the cricket ground. You can use booking plugins or customize them based on your specific needs.

    7. Real-time Score Updates:
    – For real-time score updates, consider integrating a live scoring API or implement a solution that allows the input of scores during a live match.

    8. User Management:
    – Implement user roles and permissions to manage who can update scores, edit content, and perform other administrative tasks.

    9. Responsive Design:
    – Ensure that your web application has a responsive design so that users can access and interact with it on various devices, including smartphones and tablets.

    10. Testing and Security:
    – Test your application thoroughly to identify and fix any bugs or issues. Also, prioritize the security of the application, especially if it involves user data or sensitive information.

    Keep in mind that while WordPress can be a powerful tool for web development, more complex functionalities may require a combination of existing plugins and custom development. If the requirements become highly specialized, you might also consider consulting with a web developer or agency to ensure the successful implementation of your cricket scoring web application. Also you can see this cricket schedule website for reference.

    #332354

    In reply to: BuddyPress 12.0.0

    hengstigal
    Participant

    Hello, i get the following error after Updating to 12.0. Could you please help me? 🙂

    WordPress-Version 6.4.2
    Aktives Theme: Cera (Version 1.2.0)
    Aktuelles Plugin: BuddyPress (Version 12.0.0)
    PHP-Version 8.1.26

    Ein Fehler vom Typ E_ERROR wurde in der Zeile 350 der Datei /homepages/10/d383743307/htdocs/######/wp-content/plugins/buddypress/bp-core/deprecated/12.0.php verursacht. Fehlermeldung: Uncaught Error: Call to undefined function bp_get_groups_directory_url() in /homepages/10/d383743307/htdocs/######/wp-content/plugins/buddypress/bp-core/deprecated/12.0.php:350
    Stack trace:
    #0 /homepages/10/d383743307/htdocs/######/wp-content/plugins/grimlock-buddypress/inc/widget/fields/class-grimlock-buddypress-groups-section-widget-fields.php(155): bp_get_groups_directory_permalink()
    #1 /homepages/10/d383743307/htdocs/######/wp-includes/class-wp-hook.php(324): Grimlock_BuddyPress_Groups_Section_Widget_Fields->change_defaults()
    #2 /homepages/10/d383743307/htdocs/######/wp-includes/plugin.php(205): WP_Hook->apply_filters()
    #3 /homepages/10/d383743307/htdocs/######/wp-content/plugins/grimlock/inc/widget/class-grimlock-base-widget.php(21): apply_filters()
    #4 /homepages/10/d383743307/htdocs/######/wp-content/plugins/grimlock-buddypress/inc/widget/class-grimlock-buddypress-groups-section-widget.php(29): Grimlock_Base_Widget->__construct()
    #5 /homepages/10/d383743307/htdocs/######/wp-includes/class-wp-widget-factory.php(62): Grimlock_BuddyPress_Groups_Section_Widget->__construct()
    #6 /homepages/10/d383743307/htdocs/######/wp-includes/widgets.php(115): WP_Widget_Factory->register()
    #7 /homepages/10/d383743307/htdocs/######/wp-content/plugins/grimlock-buddypress/inc/class-grimlock-buddypress.php(202): register_widget()
    #8 /homepages/10/d383743307/htdocs/######/wp-includes/class-wp-hook.php(324): Grimlock_BuddyPress->widgets_init()
    #9 /homepages/10/d383743307/htdocs/######/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    #10 /homepages/10/d383743307/htdocs/######/wp-includes/plugin.php(517): WP_Hook->do_action()
    #11 /homepages/10/d383743307/htdocs/######/wp-includes/widgets.php(1858): do_action()
    #12 /homepages/10/d383743307/htdocs/######/wp-includes/class-wp-hook.php(324): wp_widgets_init()
    #13 /homepages/10/d383743307/htdocs/######/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    #14 /homepages/10/d383743307/htdocs/######/wp-includes/plugin.php(517): WP_Hook->do_action()
    #15 /homepages/10/d383743307/htdocs/######/wp-settings.php(643): do_action()
    #16 /homepages/10/d383743307/htdocs/######/wp-config.php(116): require_once(‘/homepages/10/d…’)
    #17 /homepages/10/d383743307/htdocs/######/wp-load.php(50): require_once(‘/homepages/10/d…’)
    #18 /homepages/10/d383743307/htdocs/######/wp-login.php(12): require(‘/homepages/10/d…’)
    #19 {main}

    #332341

    In reply to: BuddyPress 12.0.0

    Mathieu Viet
    Moderator

    Hi @yatesa01

    About this:
    > The option in customizer to use round profile images is no longer present after updating to 12.0.

    It’s not an issue, we’re removed it on purpose, to avoid messing with the active Theme’s way of displaying an avatar.
    https://buddypress.trac.wordpress.org/ticket/8273

    You can easily get it back using this CSS rule:

    
    .buddypress-wrap .avatar {
    	border-radius: 50%;
    }
    
    #332332

    In reply to: BuddyPress 12.0.0

    bmoreau92
    Participant

    BuddyPress 12.0 function bp_core_get_user_domain deprecated

    Hi !

    Since version 12.0 I get a critical error.
    WordPress debug mode gives me this message :
    Deprecated: La fonction bp_core_get_user_domain est obsolĂšte depuis la version 12.0.0 ! Utilisez bp_members_get_user_url() Ă  la place. in /home/nudeoep/www/wp-includes/functions.php on line 6031

    I installed BP Classic and it resolves the problem.

    BUT when I try to change the options of my Flatsome Theme, I don’t see the regular screen but this :
    DerniÚres notes publiées (BuddyPress)
    Titre :
    Nombre max. Ă  afficher :

    It’s weird !

    Thanks in adavance four your help !

    I received this message from WordPress :

    WordPress a trouvĂ© une erreur avec l’une de vos extensions, « BP Classic »

    Une erreur de type E_ERROR a Ă©tĂ© causĂ©e dans la ligne 206 du fichier /home/nudeoep/www/wp-content/plugins/bp-classic/inc/templates/classes/class-bp-classic-templates-nouveau-latest-activities.php. Message d’erreur : Uncaught Error: Call to undefined function bp_nouveau_get_activity_filters() in /home/nudeoep/www/wp-content/plugins/bp-classic/inc/templates/classes/class-bp-classic-templates-nouveau-latest-activities.php:206
    Stack trace:
    #0 /home/nudeoep/www/wp-includes/class-wp-widget.php(535): BP_Classic_Templates_Nouveau_Latest_Activities->form(Array)
    #1 /home/nudeoep/www/wp-admin/includes/widgets.php(276): WP_Widget->form_callback(Array)
    #2 /home/nudeoep/www/wp-includes/class-wp-customize-widgets.php(1148): wp_widget_control(Array, Array)
    #3 /home/nudeoep/www/wp-includes/class-wp-customize-widgets.php(1096): WP_Customize_Widgets->get_widget_control(Array)
    #4 /home/nudeoep/www/wp-includes/class-wp-customize-widgets.php(714): WP_Customize_Widgets->get_available_widgets()
    #5 /home/nudeoep/www/wp-includes/class-wp-hook.php(324): WP_Customize_Widgets->enqueue_scripts(”)
    #6 /home/nudeoep/www/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)
    #7 /home/nudeoep/www/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
    #8 /home/nudeoep/www/wp-admin/customize.php(123): do_action(‘customize_contr
’)
    #9 {main}
    thrown

    Details of my configuration :

    WordPress version 6.4.2
    ThĂšme actif : Flatsome (version 3.18.2)
    Extension actuelle : BP Classic (version 1.2.0)
    PHP version 8.0.30

    #332331
    bmoreau92
    Participant

    Details of my configuration :

    WordPress version 6.4.2
    ThĂšme actif : Flatsome (version 3.18.2)
    Extension actuelle : BP Classic (version 1.2.0)
    PHP version 8.0.30

    #332330
    bmoreau92
    Participant

    Hi again !

    I received this message from WordPress :

    WordPress a trouvĂ© une erreur avec l’une de vos extensions, « BP Classic »

    Une erreur de type E_ERROR a Ă©tĂ© causĂ©e dans la ligne 206 du fichier /home/nudeoep/www/wp-content/plugins/bp-classic/inc/templates/classes/class-bp-classic-templates-nouveau-latest-activities.php. Message d’erreur : Uncaught Error: Call to undefined function bp_nouveau_get_activity_filters() in /home/nudeoep/www/wp-content/plugins/bp-classic/inc/templates/classes/class-bp-classic-templates-nouveau-latest-activities.php:206
    Stack trace:
    #0 /home/nudeoep/www/wp-includes/class-wp-widget.php(535): BP_Classic_Templates_Nouveau_Latest_Activities->form(Array)
    #1 /home/nudeoep/www/wp-admin/includes/widgets.php(276): WP_Widget->form_callback(Array)
    #2 /home/nudeoep/www/wp-includes/class-wp-customize-widgets.php(1148): wp_widget_control(Array, Array)
    #3 /home/nudeoep/www/wp-includes/class-wp-customize-widgets.php(1096): WP_Customize_Widgets->get_widget_control(Array)
    #4 /home/nudeoep/www/wp-includes/class-wp-customize-widgets.php(714): WP_Customize_Widgets->get_available_widgets()
    #5 /home/nudeoep/www/wp-includes/class-wp-hook.php(324): WP_Customize_Widgets->enqueue_scripts(”)
    #6 /home/nudeoep/www/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)
    #7 /home/nudeoep/www/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
    #8 /home/nudeoep/www/wp-admin/customize.php(123): do_action(‘customize_contr…’)
    #9 {main}
    thrown

    bmoreau92
    Participant

    Hi !

    Since version 12.0 I get a critical error.
    WordPress debug mode gives me this message :
    Deprecated: La fonction bp_core_get_user_domain est obsolĂšte depuis la version 12.0.0 ! Utilisez bp_members_get_user_url() Ă  la place. in /home/nudeoep/www/wp-includes/functions.php on line 6031

    I installed BP Classic and it resolves the problem.

    BUT when I try to change the options of my Flatsome Theme, I don’t see the regular screen but this :
    DerniÚres notes publiées (BuddyPress)
    Titre :
    Nombre max. Ă  afficher :

    It’s weird !

    Thanks in adavance four your help !

    Bruno

    #332325

    In reply to: BuddyPress 12.0.0

    Mathieu Viet
    Moderator

    yatesa01: I see from this other topic, it’s the Astra theme. I’m looking at it.

    Here’s the ticket about the BP Blocks regression: https://buddypress.trac.wordpress.org/ticket/9037

    #332324
    Mathieu Viet
    Moderator

    @wingflap

    12.1.0 will be a minor release. There won’t be a 13.0.0 release just like the 13th floor often lacks in building. We’ll jump to 14.0.0 for our next major release.

    How long will it take us to reach 14.0.0, it depends on the number of people who will contribute to it. 12.0.0 took us almost a year and 46 people contributed to it.

    See: https://buddypress.trac.wordpress.org/ticket/9038

    #332312

    In reply to: BuddyPress 12.0.0

    Mathieu Viet
    Moderator

    Hi @mattobiwan1982

    The Pages tab of the BuddyPress settings has been replaced by the URLs one where you can customize all BP URLs slugs. Directories, registration/activate pages are now managed ged from there. See:
    https://github.com/buddypress/buddypress/blob/master/docs/user/administration/settings/urls.md

    If you need to add some of these pages to your WordPress menus, I advise you to read:
    https://github.com/buddypress/buddypress/blob/master/docs/user/administration/navigations/README.md

    #332308

    In reply to: BuddyPress 12.0.0

    jaymzwayne
    Participant

    I don’t know if this has anything to do with the new update but every time I tried to go to customize in the themes I can’t display the page correctly since the update I’ve done the classic install it seems like it’s not compatible with my themes is there a way to go back to the original WordPress

    #332307

    In reply to: BuddyPress 12.0.0

    mattobiwan1982
    Participant

    Hi

    Can anyone tell me why when I enter the BuddyPress from WordPress settings it is not showing the Pages tab so I have no way of setting the registration, login pages etc?

    Thanks

    Matt

    #332291

    In reply to: BuddyPress 12.0.0

    chuchy10
    Participant

    When BP Classic is active the WordPress menu does not work correctly: Appearance->Customize.
    Appearance submenu entries using: …wp-admin/customize.php?return=…
    You inactivate it and it works.

    Thanks for this great work!!
    Gracias por este gran trabajo!!

    #332285
    beachcalsix
    Participant

    I have 3 websites and after the newest plugin update, the entire buddypress system crashed. All pages buddypress related give a fatal error screen. Activity, members page, profile, etc. I reverted back to the old version and it works fine again. I thought it was a plugin conflict but it is happening on multiple sites even fresh ones.
    Thanks

    Wordpress version: 6.4.2
    Buddypress version with fatal error: 12.0.0
    Buddypress version that works fine: 11.4.0

    #332273
    Varun Dubey
    Participant

    You can easily check if email functionality is working on your website by using a couple of test email plugins available online. https://wordpress.org/plugins/check-email/
    If it’s working, email functionality should also be operational. BuddyPress uses the same approach to send emails.

    #332272

    In reply to: BuddyPress 12.0.0

    Varun Dubey
    Participant

    @erotmil Custom codes need to be checked for deprecated functions. BP v12 supports the last 2 versions. https://bpdevel.wordpress.com/2022/11/20/the-way-buddypress-loads-deprecated-code-will-change-in-version-11-0-0/

    #332268

    In reply to: BuddyPress 12.0.0

    Mathieu Viet
    Moderator

    @gbordormor22

    About documentation: I agree with you. Writing what we need to do is nice. It would be even greater if you could take another step: contribute to it 😅.

    We’ve tried to get contributors to help us twice to update https://codex.buddypress.org unfortunately we were not able to get enough people to help us.

    For this particular release, we’ve made a big shift and I personally took the time to write docs about the effects for users as I wrote into the announcement post. You can read it here: https://github.com/buddypress/buddypress/blob/master/docs/user/administration/README.md

    Problem is: being in the code makes you miss important things for users. The fact we now uses the URLs BP settings tab instead of the WordPress pages we used before to set BP directory slugs and titles does not seem to be too difficult to find to me. I see reading your and some other replies it’s not that easy.

    Adding directory links to WP Menus hasn’t changed that much, here’s a direct link to the doc: https://github.com/buddypress/buddypress/blob/master/docs/user/administration/navigations/README.md

    #332248

    In reply to: BuddyPress 12.0.0

    Mathieu Viet
    Moderator

    Hi @erotmil Sorry to read about this issue, I’m not sure to understand what the custom code is doing. As you’re talking about widgets I guess it may contain some <?php dynamic_sidebar( 'name_widget_zone' ); ?>. Have you checked your error_log to see if there were some errors? About BP Classic, it contains the BP Legacy widgets, they are automatically loaded if you’re not using the Block Widgets editor, the function you mentioned was used to do this check, I believe you don’t need to care about it in your case. If your custom code is viewable from a Github Gist for example, I can look at it to see if I can find an explanation to your issue.


    @claudiovillagra
    I understand your frustration. If I often talk about BP Classic when replying to support requests about the 12.0.0 upgrade that’s because it’s the Add-on we’ve built to “neutralize” the 12.0.0 change BP Plugins might not be ready with (even if we’ve been working on 12.0.0 and communicating about it for almost a year…). I thought Woffice was a plugin but find out it was a premium theme. Unfortunately I can’t look at their code to understand the issue. If you haven’t try BP Classic, what I would do in your case would be to put up a staging site to replicate your production site and give 12.0.0 some other tests, try BP Classic and if issues are not solved with it, try to identify the issue checking the error_log file or using define( 'WP_DEBUG', true ).

    #332244

    In reply to: Buddypress invitations

    ingenxcomputers
    Participant

    thank you

    can you recommend a wordpress email plugin? that will work directly with buddypress when I press ‘send invitation’

    #332243

    In reply to: BuddyPress 12.0.0

    Mathieu Viet
    Moderator

    Hi @dangbird

    Thanks for your feedback, in version 11.4.0 we’ve (exceptionally) introduced a feature to display notifications only to admins to inform them about the massive change coming into 12.0.0. See https://buddypress.trac.wordpress.org/ticket/9007

    This feature we called “Admin notifications” is temporarily overriding the notifications for all admin users as long as one of the admin clicks on the exclamation mark to read the important message we want him to read. This message is about when to activate BP Classic to preserve backwards compatibility required by a specific config (BP Plugins not updated for the last 4 months, the deprecated BP Default standalone theme activated or the need to still use BP Legacy widgets).

    It may be the reason explaining what you saw with the Reign theme. It should disappear as soon as you read the Admin notification. Let me know if it helped you fix (or not) the issue with 12.0 for you.

    #332241

    In reply to: BuddyPress 12.0.0

    Mathieu Viet
    Moderator

    Hi @westmdresearch

    Thanks a lot for your feedback 😍. I’m happy to read you succeeded in troubleshooting issues on your side. We always try to imagine what could go wrong when we update our code but at the same time, we need to go forward. This release is very important as we’ve tried to explain as much as we could, it’s a starting point: fully complying with WordPress way of parsing requests will help us on various fields in the future. We know it’s a massive change and I feel sorry to read there are cases we were not able to anticipate: but we strongly believe it’s a needed change for the better of our next community features.

    #332239
    Mathieu Viet
    Moderator

    Hi @jane-blonde

    As we informed into an Admin notification after the 11.4.0 upgrade and at each 12.0.0 pre-releases. So it’s not an issue.

    We’ve moved Legacy widgets into the BP Classic back compatibility add-on. Since version 9.0.0 we’ve transformed these legacy widgets as block widgets.

    BP Classic

    #332238
    bastibln
    Participant

    Hey,

    there seems to be something not working properly, independent from the theme I am using and with having no plugins activated at all:

    When I enter my First and Last Name in the usual User -> Profile Dashboard from WordPress, ervything is fine. Let’s assume I choose a Nickname as well:

    First Name: Tom
    Last Name: Train
    Nickname: Tommy

    In the Public Name dropdown, I choose ‘Tommy’.
    Save it.

    Now I already have created some additional profile fields, like the gender.
    If I change my data there now, from option 1 to option 2, and I save it, and I go back to the first “Profile” tab within the WordPress Dashboard, all my name declarations are gone, except Tommy.

    Is this a known problem for someone?

    #332231

    In reply to: BuddyPress 12.0.0

    Mathieu Viet
    Moderator

    Hi @gyrus

    Sorry to read about this issue.

    We’ve built BP Classic a back compatibility Add-on, maybe you can try activating it to see if it solves the issue:

    BP Classic

    If not, I’ve explained into this reply how to rollback to 11.4.0 (you’ll need BP Classic anyway)

    BuddyPress 12.0.0

    > if you want to rollback, activate BP Classic (to get the regular directory pages back into your regular WordPress pages), then deactivate BuddyPress and BP Classic. You’ll need to manually reset the « DB Version » to the one of you version, see https://codex.buddypress.org/releases/. For instance for version 11.4.0, into the wp_options table the _bp_db_version option should be 13408. Only then download and activate a previous BuddyPress version (11.4.0).

    #332213

    In reply to: Enqueuing CSS in 12.0

    Mathieu Viet
    Moderator

    Hi @lordmatt, another way to fix it is to use this filter:

    add_filter( 'bp_enqueue_assets_in_bp_pages_only', 'return_false' );

    See: https://bpdevel.wordpress.com/2023/11/18/bp-template-pack-javascript-and-style-assets-are-now-only-loaded-into-the-community-area-of-your-site/

Viewing 25 results - 451 through 475 (of 22,644 total)
Skip to toolbar