IMPORTANT NOTE: This was only a “Proof of Concept” study about how quickly could we convert Bootstrap Themes to XOOPS. These themes are in ALPHA release, and will need some help from our XOOPS Designers before they become usable.
Therefore please DO NOT use them on production sites. However, please fork them, improve them, and help us with development.
The XOOPS Development Team is pleased to announce the release of security patches for XOOPS 2.5.8 and XOOPS 2.5.7.2.
These patches includes the latest version of PHPMailer to address a serious vulnerability. All XOOPS users are encouraged to update as soon as possible.
Both full distributions and patch files (from the most recent prior release) for both the 2.5.7 and 2.5.8 series are available.
Any users that are running older XOOPS versions are advised to update to XOOPS 2.5.8.1 now.
In the next few weeks the XOOPS Website will be very busy, with a lot of work happening in the front of you!
Instead of making a secret out of it, and then creating a huge splash out of it, we’ve decided to just go ahead and make changes to the Website as we go.
What is happening:
1) We are moving to PHP 7. Originally we were on 5.4, and this weekend we moved to PHP 5.6, as as soon as our host offers PHP 7, we’ll be ready.
2) We’ve also moved the Website to the latest XOOPS Core, so we can test it here before we officially release it.
3) We are also updating all modules that are being used here, which will help us, of course with your help, to discover any bugs
We have updated the NewBB Forums to the latest version, as well as News. We’ll be converting soon the News to Publisher, as strategically that’s what we want to invest our time in.
And we’ll be adding some new cool modules, like the one upcoming wgTimelines developed by Goffy from Germany. We’ll transition our “XOOPS Innovators” and “XOOPSer of the Month” awards there. The work on the converting the “XOOPS Innovators” to the wgTimelines has already started – you can check it out herehttps://xoops.org/modules/wgtimelines/
What else?
We have moved modules developed by Wishcraft to one location on GitHub (read more here), so you can check them out, fork, and contribute back.
We have also created one GitHub location for various XOOPS D3 modules. If you’re curious what the D3 modules are, please read more here
Of course, we hope that you’ll help us on this journey as we’re moving closer to the next release of XOOPS
And in case you were wondering, yes, we’re looking for a new responsive theme for this updated Website! So if you would like to design a new theme for us, please let us know… XOOPS Web Application System
When you’re browsing the web, how quickly do you navigate elsewhere if a website isn’t instantly loading? We all know from experience that every second counts. If your website takes too long to load, visitors won’t hesitate to move on—sometimes straight to your competitors.
Faster load times not only improve user satisfaction but also boost your search engine rankings and ultimately drive more conversions.
That’s why you’re going to love using our new Site Speed Tool. It can quickly identify areas impacting your site’s Core Web Vitals (CWV), like load times, interactivity, and visual stability and provides actionable insights and recommendations, making it easier to optimize your site’s performance and deliver a smoother, faster user experience.
Nearly 70% of consumers admit that page speed impacts their willingness to buy from an online retailer.
Almost half of consumers say they’ll try to refresh a page at least once when it takes 3 seconds to load. But 22% say they’ll close the tab, and 14% say they’ll visit a competitor’s site.
47% of consumers expect a web page to load in 2 seconds or less.
If a website takes more than three seconds to load, 40% of the people will leave that site.
Website performance plays a critical role in the success of any online business. Slow websites will cost you not only visitors but also potential revenue. Investing in performance optimization could be the difference between closing a sale and losing out to a competitor.
A faster website gives you a competitive edge by capturing traffic from slower sites. Visitors are more likely to stay, explore, and convert into customers when your site loads quickly. Speed isn’t just a nice-to-have—it’s a key driver of business growth.
Optimize your WordPress site for lightning-fast performance
Is your WordPress site as fast as it could be? Test the speed of your WordPress site with free our Site Speed Tool and get detailed performance metrics and tailored recommendations with just a few clicks. Simply enter any public WordPress URL, and we’ll run real-time tests on your site to assess its performance.
Our tool evaluates key areas, such as:
Loading speed: How fast your site loads for users.
Core Web Vitals: Metrics that focus on user experience, including loading, interactivity, and visual stability.
Historical performance: Tracking your site’s performance over time to spot trends and areas for improvement.
Once analyzed, you’ll receive an easy-to-understand performance score and WordPress-specific, AI-enhanced recommendations to boost your website’s speed and overall performance.
If you already have a site on WordPress.com with a Business or Commerce plan, you can also easily access the speed test directly in your dashboard. Test your performance across all of your sites to better understand correlations between site changes and performance.
Get weekly performance change alerts
Want to stay ahead of performance issues? Sign up for weekly performance change alerts, which provide a comprehensive overview of your website’s metrics over the last handful of weeks. These reports will highlight trends, performance fluctuations, and areas where further optimization is needed—keeping you informed and in control of your website’s health.
Test your site today
Your website’s performance can make or break your success online. With our easy-to-use performance measurement tool, you can take the guesswork out of optimizing your site.
Test your URL now for free and get personalized recommendations to ensure your site performs at its best, or head to the Performance tab in your site’s Hosting Overview menu to get automatic performance data about your WordPress.com sites.
Don’t leave your website’s success to chance—start optimizing today.
The third release candidate (RC3) for WordPress 6.7 is ready for download and testing!
This version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it’s recommended that you evaluate RC3 on a test server and site.
Reaching this phase of the release cycle is an important milestone. While release candidates are considered ready for release, testing remains crucial to ensure that everything in WordPress 6.7 is the best it can be.
You can test WordPress 6.7 RC3 in four ways:
Plugin
Install and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream).
Direct Download
Download the RC3 version (zip) and install it on a WordPress website.
Command Line
Use the following WP-CLI command: wp core update --version=6.7-RC3
WordPress Playground
Use the 6.7 RC3 WordPress Playground instance (available within 35 minutes after the release is ready) to test the software directly in your browser without the need for a separate site or setup.
Get a recap of WordPress 6.7’s highlighted features in the Beta 1 announcement. For more technical information related to issues addressed since RC2, you can browse the following links:
WordPress is open source software made possible by a passionate community of people collaborating on and contributing to its development. The resources below outline various ways you can help the world’s most popular open source web platform, regardless of your technical expertise.
Get involved in testing
Testing for issues is critical to ensuring WordPress is performant and stable. It’s also a meaningful way for anyone to contribute. This detailed guide will walk you through testing features in WordPress 6.7. For those new to testing, follow this general testing guide for more details on getting set up.
If you encounter an issue, please report it to the Alpha/Beta area of the support forums or directly to WordPress Trac if you are comfortable writing a reproducible bug report. You can also check your issue against a list of known bugs.
For plugin and theme authors, your products play an integral role in extending the functionality and value of WordPress for all users.
Thanks for continuing to test your themes and plugins with the WordPress 6.7 beta releases. With RC3, you’ll want to conclude your testing and update the “Tested up to” version in your plugin’s readme file to 6.7.
If you find compatibility issues, please post detailed information to the support forum.
The second release candidate (RC2) for WordPress 6.7 is ready for download and testing!
This version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it’s recommended that you evaluate RC2 on a test server and site.
Reaching this phase of the release cycle is an important milestone. While release candidates are considered ready for release, testing remains crucial to ensure that everything in WordPress 6.7 is the best it can be.
You can test WordPress 6.7 RC2 in four ways:
Plugin
Install and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream).
Direct Download
Download the RC2 version (zip) and install it on a WordPress website.
Command Line
Use the following WP-CLI command: wp core update --version=6.7-RC2
WordPress Playground
Use the 6.7 RC2 WordPress Playground instance (available within 35 minutes after the release is ready) to test the software directly in your browser without the need for a separate site or setup.
Get a recap of WordPress 6.7’s highlighted features in the Beta 1 announcement. For more technical information related to issues addressed since RC1, you can browse the following links:
WordPress is open source software made possible by a passionate community of people collaborating on and contributing to its development. The resources below outline various ways you can help the world’s most popular open source web platform, regardless of your technical expertise.
Get involved in testing
Testing for issues is critical to ensuring WordPress is performant and stable. It’s also a meaningful way for anyone to contribute. This detailed guide will walk you through testing features in WordPress 6.7. For those new to testing, follow this general testing guide for more details on getting set up.
If you encounter an issue, please report it to the Alpha/Beta area of the support forums or directly to WordPress Trac if you are comfortable writing a reproducible bug report. You can also check your issue against a list of known bugs.
For plugin and theme authors, your products play an integral role in extending the functionality and value of WordPress for all users.
Thanks for continuing to test your themes and plugins with the WordPress 6.7 beta releases. With RC2, you’ll want to conclude your testing and update the “Tested up to” version in your plugin’s readme file to 6.7.
If you find compatibility issues, please post detailed information to the support forum.
In nearly 1,000 days, the WordPress community has created 1,000 Block themes—coming together to use the full potential of the Site Editor and unleash new creative possibilities for everyone.
First introduced in WordPress 5.9, Block themes have steadily evolved, improving flexibility and functionality for themers, users, and agencies alike. Now, design tools allow customizing almost every detail. With style variations, users can change the overall look of their site in a few clicks. You can even use curation options to customize the editing process itself. But we’re not done! We can’t wait to keep pushing Block themes even further. Thank you to every early adopter who, by embracing early features with passion, helped shape the Block themes we love today with feedback and testing.
If you haven’t yet explored Block themes, check out some of the resources below to get inspired:
The first release candidate (RC1) for WordPress 6.7 is ready for download and testing!
This version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it’s recommended that you evaluate RC1 on a test server and site.
Reaching this phase of the release cycle is an important milestone. While release candidates are considered ready for release, testing remains crucial to ensure that everything in WordPress 6.7 is the best it can be.
You can test WordPress 6.7 RC1 in four ways:
Plugin
Install and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream).
Direct Download
Download the RC1 version (zip) and install it on a WordPress website.
Command Line
Use the following WP-CLI command: wp core update --version=6.7-RC1
WordPress Playground
Use the 6.7 RC1 WordPress Playground instance (available within 35 minutes after the release is ready) to test the software directly in your browser without the need for a separate site or setup.
Get a recap of WordPress 6.7’s highlighted features in the Beta 1 announcement. For more technical information related to issues addressed since Beta 3, you can browse the following links:
WordPress is open source software made possible by a passionate community of people collaborating on and contributing to its development. The resources below outline various ways you can help the world’s most popular open source web platform, regardless of your technical expertise.
Get involved in testing
Testing for issues is critical to ensuring WordPress is performant and stable. It’s also a meaningful way for anyone to contribute. This detailed guide will walk you through testing features in WordPress 6.7. For those new to testing, follow this general testing guide for more details on getting set up.
If you encounter an issue, please report it to the Alpha/Beta area of the support forums or directly to WordPress Trac if you are comfortable writing a reproducible bug report. You can also check your issue against a list of known bugs.
For plugin and theme authors, your products play an integral role in extending the functionality and value of WordPress for all users.
Thanks for continuing to test your themes and plugins with the WordPress 6.7 beta releases. With RC1, you’ll want to conclude your testing and update the “Tested up to” version in your plugin’s readme file to 6.7.
If you find compatibility issues, please post detailed information to the support forum.
At the heart of our community is our shared pledge to create a space that is harassment-free, welcoming, and inclusive for all. Our Community Code of Conduct already outlines a clear set of expectations, while also providing examples of unacceptable actions. Today, we are reinforcing our values by adding another element to our list of unacceptable behaviors: Publishing private messages without consent.
Why This Addition Matters
The relationships we build within our community often involve private discussions. These conversations may involve sensitive matters, personal experiences, or simply casual exchanges. Regardless of the content, every individual should feel confident that their private communications will remain private unless they grant explicit permission to share them.
Sharing private messages without consent is a breach of trust that can also lead to unintended harm, including emotional distress or misrepresentation. When members of our community feel they cannot trust others in their personal conversations, it undermines the collaborative spirit that is crucial to our collective success.
How This Change Protects the Community
By explicitly addressing the publication of private messages without consent, we are reinforcing an existing unacceptable behavior in our Community Code of Conduct: Other conduct which could reasonably be considered inappropriate in a professional setting. Sharing private communications without permission is a clear violation of professional integrity.
This new addition ensures that private messages receive the same level of protection as personal information and that sensitive communications shared in confidence will not be disclosed without prior consent. An important exception to this is when sharing private messages is necessary for reporting incidents or concerns to the Incident Response Team, as part of our commitment to maintaining a safe and respectful environment.
Ultimately, this change encourages honest, constructive engagement across all levels of participation.
Moving Forward Together
The strength of our community lies in the trust we place in one another. By clarifying and reinforcing our expectations, we are taking another step toward maintaining an inclusive, respectful, and safe environment for everyone.This new addition will take effect immediately, and violations will be handled in accordance with our existing enforcement guidelines. Together, we can ensure our community remains a place of collaboration, trust, and mutual respect.
When I send a message from Gmail.com to my number@vtext,com or my vzwpix.com I get an error message 451 server temporarily unavailable AUP#CDRBL & never receive the message. My answering service uses gmail to send to all carriers & everyone of them work except Verizon. It worked for the longest time & for about a week or 2 stopped working on Verizon. Any suggestions?
Thx for replying. Interestingly, a bunch of email -to -texts to my phone (via mynumber(at)vzwpix.com and vztext.com) arrived this afternoon after being sent this morning. Then I was able to successfully send some real-time as I tested this afternoon. Now, however, it seems to not work again.
