Wordpress News

WordPress 5.3 Beta 3

Wordpress News - Tue, 10/08/2019 - 20:58

WordPress 5.3 Beta 3 is now available!

This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version.

You can test the WordPress 5.3 beta in two ways:

WordPress 5.3 is slated for release on November 12, 2019, and we need your help to get there.

Thanks to the testing and feedback from everyone who tested beta 2 (and beta 1) over 60 tickets have been closed in the past week.

Some highlights
  • Fixes and enhancements in the admin interface changes introduced in previous 5.3 beta releases.
  • Wording changes in login screen (#43037).
  • Improved accessibility in media upload modal (#47149).
  • Changes in the way the new error handling with images works (#48200).
  • MediaElement.js has been updated from 4.2.6 to 4.2.13 (#46681). The script is now also being loaded in the footer again. This fixes a regression that happened two years ago, so might be worth noting (#44484).
  • Update to the REST API media endpoint to allow resuming of uploads (#47987).

In addition to these, Beta 3 landed a number of small consistency and polish changes to the REST API, including an improvement to the permissions check used when editing comments, a fix for post type controller caching edge cases, and most importantly, the ability to use the _embed parameter to access the full data for a post using the /wp/v2/search endpoint.

Developer notes

WordPress 5.3 has lots of refinements to polish the developer experience. To keep up, subscribe to the Make WordPress Core blog and pay special attention to the developer notes tag for updates on those and other changes that could affect your products.

How to Help

Do you speak a language other than English? Help us translate WordPress into more than 100 languages!

If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac where you can also find a list of known bugs.

People of WordPress: Alice Orru

Wordpress News - Sat, 10/05/2019 - 04:24

You’ve probably heard that WordPress is open-source software, and may know that it’s created and run by volunteers. WordPress enthusiasts share many examples of how WordPress changed people’s lives for the better. This monthly series shares some of those lesser-known, amazing stories.

Meet Alice Orru, from Sardinia, Italy.

Alice Orru was born in Sardinia, an island in the middle of the Mediterranean Sea. As a child, she dreamt of becoming a flight attendant, traveling the world, and speaking many foreign languages.

Unable to meet the height requirements of her chosen profession, Orru ended up choosing a different path in life, following the Italian mantra: “You have to study something that will guarantee a stable and secure job for life.”

The unemployment rate in Sardinia is very high, a challenge shared throughout the surrounding islands. In addition to that, Alice wasn’t that keen on having the same job all her life, as her parents had.

When Orru was 22 she moved to Siena, Tuscany, to finish her studies. That is when she created her first personal blog. The website was built on an Italian platform named Tiscali, which she later migrated to WordPress.com.

After 2 years in Tuscany Orru moved to Strasbourg, France. She studied French and worked several jobs while living there. Her first serious job was in Milan – working 40 hours/week in the marketing department of a large, international company. She found herself surrounded by ambitious colleagues and a boss who constantly requested extra —unpaid— working hours per day.

Alice Orru Choices, choices, choices…

Alice gave up blogging because she wasn’t feeling inspired enough to write. She questioned whether she really wanted to do that job forever; working 10 hours per day under the neon lights of an office. It forced her to set aside her dreams for the time being, and for a while, she mainly lived for the weekends.

Alice decided to leave the job and moved to Barcelona, Spain, all by herself, in 2012.

After a few months of intense Spanish learning at the university, she found a job in an international clinic as a “Patient Coordinator.” Orru assisted international patients coming to Barcelona for their treatments. She acted as their translator, interpreter and administrative consultant. 

Patients came from Italy, France, England, Morocco, Senegal, and several other countries. Alice was so inspired by some of their stories, that she started to write again: She dusted off her WordPress blog and filled it with stories about her new life in Barcelona and some of the women she met at the clinic. “I was feeling stronger and more independent than ever,” Orru expressed.

Technical issues led to unexpected opportunities

In the summer of 2015, Alice was writing on her blog and got stuck with a technical problem. While she was searching through the WordPress.com documentation, she saw a pop-up in the bottom right corner of her screen. It was a staff member of Automattic, checking if she needed help. They chatted for a few minutes and the problem was solved. Alice left the chat with one question, though: how did that person on chat find a support job with WordPress?

Alice found the official WordPress job page: jobs.wordpress.net and noticed a job offer that caught her attention: WP Media, a French startup, was looking for a polyglot and remote customer service teammate for one of their plugins, WP Rocket. She read their requirements: fluency in English, French and possibly other languages, excellent experience with WordPress, and some coding skills.

She knew she didn’t meet all the requirements, but could speak 4 languages, and she had a WordPress blog. She didn’t know anything about PHP, though. Orru had been a WordPress.com user for years and knew she was ready to learn more.

Orru wrote a cover letter and sent her CV. A Skype interview was conducted and several days later she received the news that she had gotten the job! 

A steep learning curve

The early days in her new job were intense. Alice felt inexperienced but was supported by her teammates. She started studying and reading everything about WordPress for beginners. Initially, she answered easy tickets from customers. All the while her teammates were sending useful material to read, setting up video-calls for 1 to 1 training, and encouraging her the entire time.

Soon, Orru was replying to customers whose first language was either Spanish or Italian in their native language. This was much appreciated and resulted in several happy comments. Until that moment the plugin’s support had been offered only in English and French.

Finding her way in the WordPress community

At WordCamp Paris 2016, one of Alice’s teammates introduced her to how the WordPress community collaborated and kept in contact through Slack.

“You speak multiple languages, why don’t you try to contribute to the polyglots team?” he asked.

Alice knew very little about contributing to WordPress. She had only been working for WP Media for 6 months and didn’t feel ready to dive into a new challenge and start also contributing to WordPress.

Yet, curiosity led her to join both the local Italian and the global WordPress Community on Slack. For the first few months, she mainly observed what was happening the channels. Then, she attended WordCamp Milan and met some members of the Italian Polyglots team.

It was love at first string! Laura, one of the General Translation Editors (GTE) for Italy, taught her how to start contributing and translating, following the polyglots guidelines. She also told her about the Italian community’s big efforts to work together, consistently, to boost and grow WordPress related events in Italy.

With her teammates’ encouragement, Orru applied to WordCamps as a speaker and gave her first talk in December 2016 at WordCamp Barcelona. After that, she both spoke at WordCamp Torino on April 2017 and at WordCamp Europe in 2017.

Alice Orru speaking at WordCamp Europe, in Paris, in 2017 Dreams evolve, all the time!

Orru knows that her experiences are not just due to luck. She used her previous skills and passions and adapted them to a new career and life path.

“We all have some skills; and if we don’t know which they are exactly, we should take some time to make a list of the things we’re really good at. With that in mind, just try. Apply. Get involved. Don’t get stuck in the feeling of ‘I can’t do it because I don’t know enough’. So that’s what I did. Without even realizing it, I started putting into reality the dream of the little girl who was born on an island and wanted to travel and speak different languages.WordPress made this possible. I’m now part of a big community, and I am proud of it.”

Alice Orru

This post is based on an article originally published on HeroPress.com, a community initiative created by Topher DeRosia. HeroPress highlights people in the WordPress community who have overcome barriers and whose stories would otherwise go unheard.

Meet more WordPress community members over at HeroPress.com!

Catalog Lite

Drupal Themes - Fri, 10/04/2019 - 13:41

DCF Theme

Drupal Themes - Wed, 10/02/2019 - 15:44

The DCF Theme project consists of a base theme and a starter theme, DCF Base and DCF Starter, respectively.

DCF Base

DCF Base is a Drupal base theme that contains generic templates and implements generic preprocess functions for the purpose of adding DCF classes to Drupal's rendered markup. It is meant to be updated over time as new features are added upstream.

DCF Starter

DCF Starter is a starter theme that provides scaffolding on which themers can build front-end, DCF-based Drupal projects. It includes 1) a Node.js project that downloads DCF as a dependency and 2) a Gulp-based workflow. The sub-theme, itself, it not meant to receive upstream updates. Upstream updates from DCF should be managed through the included Node.js project.

The Month in WordPress: September 2019

Wordpress News - Wed, 10/02/2019 - 08:05

September has been a particularly busy month in the WordPress community—a lot of important work has been done as everyone in the project works towards an upcoming major release. Read on to find out more about this and everything else that has been going on over the past month.

WordPress 5.2.3 Security and Maintenance Release

Early in September, version 5.2.3 of WordPress was released as a security and maintenance release. Sixty-two individuals contributed to its 29 fixes and enhancements.

The security issues fixed in this release owe thanks to numerous people who disclosed them responsibly. You can read more about the vulnerability reporting process in the Core handbook.

Want to get involved in building WordPress Core? Follow the Core team blog, and join the #core channel in the Making WordPress Slack group.

WordPress 5.3 Enters Beta

WhileWordPress 5.3 is slated for release on November 12, it has already entered the beta phase with the second beta release being made available at the end of September. As this is a major release, it will feature a number of new features and enhancements, including significant improvements to the block editor, updates to the Site Health component, new block APIs, accessibility updates, and much more.

You can test the 5.3 beta release by installing the WordPress Beta Tester plugin on any WordPress site, although as this is software that is currently in development, we don’t recommend installing it on a live site.

Want to get involved in building this release? Test the beta, follow the Core team blog, and join the #core channel in the Making WordPress Slack group.

Date/Time Component Improvements

For over a year, contributors involved in the Date/Time component of WordPress Core have been working hard on the “wp_date” project. The goal of this project is to fix and streamline the way that Core handles times and dates throughout the platform.

This ambitious project has seen incremental changes over the last few Core releases. The upcoming 5.3 release will include the final and most significant changes to the component, bringing much-needed stability to time handling in WordPress Core.

Want to get involved in the Date/Time component of WordPress Core? Learn more about it, follow the Core team blog, and join the #core-datetime channel in the Making WordPress Slack group.

New Theme Review Team Structure

After recent discussions around the goals of the Theme Review team, some changes have been made to the leadership structure of the team. The team leads are now ‘representatives’ of different areas of the work that they do. This flat structure allows for representatives to work in more loosely defined areas so they contribute to the team in more diverse ways, and helps the team to be more focused on setting and achieving their goals. The new structure is outlined in the team handbook.

Want to get involved in reviewing themes for WordPress? Follow the Theme Review team blog, and join the #themereview channel in the Making WordPress Slack group.

New Default Theme: Twenty Twenty

The upcoming 5.3 release will also include a new default theme for WordPress, Twenty Twenty. This theme will have a strong focus on readability and accessibility while being optimized for the block editor that first shipped with WordPress 5.0.

Development of Twenty Twenty has been going quickly, with a recent update showing more of the design and layouts that you can expect when the theme is released with WordPress 5.3 in November.

Want to get involved in building Twenty Twenty? You can contribute on GitHub, follow the Core team blog, and join the #core channel in the Making WordPress Slack group.

Further Reading:

Have a story that we should include in the next “Month in WordPress” post? Please submit it here.

Restaurant DS

Drupal Themes - Tue, 10/01/2019 - 16:36

Restaunt DS is a responsive Drupal 8 theme for Hotel & restaurant related websites.

Features

  • Drupal 8.7 core
  • Multiple Pages
  • Booking Reservation Page

Live Demo


Download Demo Site

Downloaded Demo login credentials : admin / admin@ds


Credits

Designed by Melody Themes

Drupal theme by DrupalSlave

WordPress 5.3 Beta 2

Wordpress News - Mon, 09/30/2019 - 21:43

WordPress 5.3 Beta 2 is now available!

This software is still in development, so we don’t recommend running it on a production site. Consider setting up a test site to play with the new version.

You can test the WordPress 5.3 beta in two ways:

WordPress 5.3 is slated for release on November 12, 2019, and we need your help to get there.

Thanks to the testing and feedback from everyone who tested beta 1, over 45 tickets have been closed since then.

Some highlights
  • Work continues on the block editor.
  • Bugs fixed on Twenty Twenty.
  • Accessibility bugs fixes and enhancements on the interface changes introduced with 5.3 beta 1:
    • Iterate on the admin interface
    • Reduce potential backward compatibility issues
    • Improve consistency between admin screens and the block editor
    • Better text zoom management
  • Support rel="ugc" attribute value in comments (#48022) – this particular ticket shows the WordPress project ability to integrate quick solutions to things that are changing unexpectedly – like Google new features.
Developer notes

WordPress 5.3 has lots of refinements to polish the developer experience. To keep up, subscribe to the Make WordPress Core blog and pay special attention to the developers notes for updates on those and other changes that could affect your products.

How to Help

Do you speak a language other than English? Help us translate WordPress into more than 100 languages!

If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac where you can also find a list of known bugs.

WPTavern: Preparing Themes For WordPress 5.3

Wordpress Planet - Mon, 09/30/2019 - 16:45

Now that WordPress 5.3 Beta 1 is open for testing and with the official release slated for November 12, it’s time for theme authors to begin making sure their themes are ready for several changes.

Most work will revolve around the block editor. WordPress 5.3 will include versions 5.4 – 6.5 of the Gutenberg plugin, a total of 12 releases. This makes for a lot of ground to cover. The next release includes breaking changes.

For themes without custom block styles, little should change. However, theme authors who have been building custom block designs will likely have some work to do if they haven’t kept up with the changes in the Gutenberg plugin over the past several months.

Block Style Variations API Introduced

WordPress 5.3 introduces new server-side block style functions. This means that theme authors who prefer PHP can now register custom block style variations without writing JavaScript code.

The block styles feature allows theme authors to register custom styles for individual blocks. Then, they must apply custom CSS to these styles in the editor and the front end.

The new functions are basic one-to-one matches to their JavaScript counterparts. Block styles still need to be registered on a per-block basis. Support for registering single styles to multiple blocks at once hasn’t landed in core.

New Block HTML Creates Breaking Changes

Despite WordPress’ commitment to backward compatibility over the years, the Gutenberg team hasn’t maintained that approach with blocks. Block HTML output in the editor and the front end has changed for some blocks. These changes will break custom theme styles in many cases.

The following blocks have potential breaking changes for themes:

  • Group: A new inner container element was added to the markup.
  • Table: A wrapper element was added and the block class moved to the wrapper.
  • Gallery: Like the table block, it received the same wrapper element treatment. Galleries also support a caption for the entire gallery block.

In my tests, the gallery block had the most obvious breaking changes. Depending on how it is styled, users could be looking at a single column of images instead of their selected number. The core development blog has a complete overview of the HTML changes along with code examples for addressing issues.

It’d be interesting to see if the Gutenberg team makes similar HTML changes with other blocks in the future. Such changes make it tough for theme authors to maintain support between versions of WordPress and versions of the Gutenberg plugin. It also bloats CSS code when attempting to maintain compatibility. Adding an extra element doesn’t typically break things. However, moving an element’s class to another element is a dumpster fire waiting to happen. If these types of changes continue to happen, it could turn some theme authors away from supporting the block editor at a time when core needs to be encouraging more authors to design around it.

New Block Classes Added

Several new CSS classes are making their way into 5.3. For themes that remove core block styles on the front end, they need to add support for the classes to their theme’s stylesheet.

WordPress is doing away with inline styles for left, right, and center text alignment. This is a welcome change because it moves CSS to its appropriate place, which is in a stylesheet. Theme authors need to make sure they support these new classes for the following blocks.

  • Heading
  • Paragraph
  • Quote
  • Verse

The columns block no longer supports column-specific class names. Version 5.3 supports custom column widths, which are handled with inline styles. It’s unlikely this will break most themes, but it’s worth testing.

The separator block now supports custom colors. It is given both the text and background color class names on the front end. This allows theme authors to utilize the styling method they prefer. Ideally, a border color class would exist, but the block editor does not yet support selecting a custom border color.

Quick developer tip: if your theme uses a border color for the separator block, use currentColor to handle custom colors.

Profile Zymphonies Theme

Drupal Themes - Mon, 09/30/2019 - 07:04

Profile Zymphonies Theme is the perfect website solution for developers, speakers, coaches, personal trainers, and other professionals who required to showcase their skills. Display your personal details on your website in the most professional way to attract recruiters and other audience. Read more

Live Demo Advanced Themes

Features
  • Drupal 8 core
  • Bootstrap v4
  • Mobile-first theme
  • Social media links
  • Designed using Sass & Compass
  • Custom slider - Unlimited image upload
  • Personal info
    • About
    • Location
    • Technologies used
    • Companies worked
Most installed Zymphonies theme Contact Zymphonies

Have Queries? Click here to contact Zymphonies

  • Free theme customization & additional features
  • Drupal custom theme development
  • Drupal website design & development
  • Drupal website migration

Sponsored by Zymphonies

Stack DD

Drupal Themes - Sun, 09/29/2019 - 06:02

Stack DD is a responsive Drupal 8 theme.

Features

  • Drupal 8.7 core
  • Single Page
  • Static side Menu bar

Live Demo

Download Demo Site

It is highly recommended to install the demo site and customize it to get the exact look.

Downloaded Demo login credentials : admin / admin@ds


Credits

Designed by Templatemo

Drupal theme by DrupalSlave

Flash

Drupal Themes - Sat, 09/28/2019 - 16:25

Flash is a "Starting Theme" which is optimized for Thunder Publishing Distribution.
It is based on Bootstrap Theme and simplify some things to use it directly or to create simple sub templates.

WPTavern: Secure the News Project Finds 93% of Major Publishers Offer HTTPS Encryption by Default

Wordpress Planet - Fri, 09/27/2019 - 23:58

Secure the News is a project that was created by the Freedom of the Press Foundation in 2016 to track HTTPS encryption across major news organizations’ websites. It lists the publications and automatically scores them on a scale of 0-100, based on HTTPS implementation according to best practices, as defined by General Services Administration (GSA) Pulse’s current criteria for modern and secure HTTPS deployment. The score is converted to an A-F letter grade.

The primary benefits of news organizations adopting HTTPS include reader privacy and website security, but there are also other positive byproducts, such as protecting sources and preventing censorship. Secure the News provides some interesting data in its campaign to encourage more broad HTTPS adoption.

In 2018, after one year of collecting data on HTTPS encryption at more than 130 major world news sites, the project found that HTTPS was available on 2/3 of the sites it monitors (89 of 131), up from 1/3 in 2016. Approximately 60% of news organizations offered HTTPS encryption by default in 2018 and that number is up to 93% today.

Most of the WordPress-powered major news sites, such as Ars Technica, Time and the New York Post, get a B ranking, with the exception of TechCrunch and Quartz, which both scored an A.

The most recent addition to the project is the ability to sort publications by region on the homepage. Publications based in North America and Europe lead the world in having the most secure HTTPS implementations. Asia has a smaller percentage of major news sites with a score of A- or higher. Some smaller regions, such as the Middle East and North Africa, Oceana, and South America, list just a handful of news organizations but they all have a score of B or higher. Secure the News is just getting started with this feature and is accepting feedback on the project’s GitHub account.

In addition to promoting HTTPS adoption, the team behind Secure the News is also considering broadening its coverage to measure other ways that news sites are delivering secure content, such as whether the site has an onion service, is Tor project friendly, or has a confidential tip line. The project also has more news sites to add and a long list of improvements they want to make to the metrics used to rank sites.

The code for Secure the News is open source (licensed under the GNU AGPL) and available on GitHub for anyone who wants to contribute or fork it for use with other site categories where browsing might be sensitive, such as libraries, adult sites, educational institutes, or medical facilities.

WPTavern: Rebirth of Creativity: Gutenberg and the Future of WordPress Themes

Wordpress Planet - Fri, 09/27/2019 - 18:56

I began using WordPress in 2005. I’d already been learning HTML and CSS for a couple of years. I even had a home-brewed blog that pulled posts from plain text files at one point. I knew enough JavaScript to do pop-up alerts and other annoying things that served no purpose and made for a poor user experience, even if they were fun for me.

This was my second attempt at using WordPress. This time it was after a botched go of making PHP Nuke behave how I wanted. I had big dreams for my website but lacked the coding skills to make them happen. WordPress was simple enough to hack for a novice like me at the time. Sure, I broke my site more times than I could count, but I managed to put together my first real theme.

I popped open Photoshop; grabbed a few images from Angel, my favorite TV show at the time; and began my work. I’d recently watched Soul Purpose, an episode that explored whether the titular character was truly the hero mentioned in an ancient prophecy. It was foretold that the vampire with a soul would shed his demon half and live as a human. It explored themes of the character’s place in the world. At 21 years old, it’s the sort of episode that resonated with a young man who was also looking for his place. I thought it fitting to work that into my theme’s design and began hacking away at a header for my theme.

Screenshot of my first WordPress theme header.

At that time, there was this loosely-connected underground of themers and hobbyists who were building WordPress themes based on their favorite TV series, movies, comic books, and more. That was my first real introduction to WordPress. These people were not building themes for profit. They were searching for their place in this small corner of the internet. At most, some were looking for validation from like-minded people who might enjoy their art. It was about creation for the sake of creation. Anyone could be an artist with a simple lesson in CSS, an image manipulation program, and enough grit to pour their soul into the project for a few hours.

If there were ever a time that WordPress themes died, it was when the hobbyists who built for pure passion were overshadowed by business interests.

Don’t get me wrong; business interests played a crucial role in propelling WordPress to become the most dominant CMS in the world. However, the balance has clearly shifted in favor of building WordPress themes for business and ecommerce rather than for the enthusiasts who just want to create. Other platforms have better catered to these users and filled in the gaps left open by WordPress. Tumblr became a safe-haven for popular culture fans. DeviantArt a home for artists. Wattpad for aspiring writers and fanfic lovers.

Somewhere along the way, we lost the innocence and artistry of building WordPress themes for the pure fun of it. WordPress grew up and WordPress themes along with it.

Today’s Themes Are Not Tomorrow’s

In his post, The End of WordPress Themes is in Sight, Ben Gillbanks said, “Themes as we know them will no longer be made.” It is a bleak look at the future of WordPress theming. He notes that he doesn’t believe that he’ll be able to make a living building WordPress themes in the next couple of years.

His worries are warranted. They have been shared by several theme authors over the past couple of years as the block editor (Gutenberg) was making its way into core WordPress. The official theme review team has discussed the team’s future role surrounding the coming changes.

Gillbanks’ post comes on the heels of a post written by Matias Ventura on defining content block areas. Essentially, the idea is for WordPress to allow users to edit areas outside of the post content via the block editor. Anything from the header, footer, sidebar, or otherwise would likely be fair game.

In such a system, themes would be relegated to defining block areas, providing base styles, and designing block output. In many ways, this is what WordPress themes should be. Some might say that WordPress is putting themes back into their proper place of simply styling content. With the behemoth themes with hundreds or thousands of features we’ve seen over the past few years, this could be a welcome change.

There’s huge potential for designers to step up and make their mark. I, for one, wouldn’t mind seeing CSS artists unleashed in the WordPress theme ecosystem.

Gillbanks went on to say:

There are definite benefits to doing this from a user’s perspective – they will have full control of their site – but it’s going to result in some very boring website layouts.

This is the point where I’ll respectfully disagree. Putting control in the hands of non-designers will be anything but boring.

Do we all so easily forget the days of GeoCities? The websites built from it may have been horribly inaccessible. They may have blared midi files as soon as you opened a webpage. They may have even had a flashing, scrolling marquee zipping across the header. Boring is not the word I’d use to describe them.

As much as many of us want to put those days behind us (Come on, you had one of those sites at one point, right? Tell the truth.), there was something fascinating about it all. Real people built these sites because they were fun. The sites told you something about that person. It was a deeply personal look into this stranger’s world. Sometimes it was just a bunch of junk spewed onto the screen, but most sites were a reflection of the site owners at that point in time.

It was ugly and beautiful all the same.

Web developers and designers joke about those dark days of the web. It’s easy to look back at sites from the ’90s and cringe at the silliness (It makes you wonder what designers of 2050 will think about today’s designs, doesn’t it?). I choose to look fondly upon those days. It was a time before I became a “designer” with rules to follow.

But, here’s the important point. We are not the arbiters of the web. It’s all about the user. If someone wants a blinking Justin Bieber GIF in their site header, more power to them. It’s the developer’s job to enable the user to do this in an easy-to-configure way.

Wait? So Geocities is your argument for full-site editing in WordPress?

Understanding why WordPress should become a full-site editor means understanding the average user. Developers are more apt to view things in a structured manner. I spent over a decade honing my development skills. Logic and order are old friends.

With end-users, things may seem a bit more chaotic. A teenager might want to plaster a picture of her favorite band anywhere she wants on her site. A soccer mom might want to show her kid slamming home the winning goal. A poet may want to showcase one of his poems as a background image on his blog. Humans are creative beings. While our unique brand of artistry might not appeal to others, it’s still something we crave to share.

It’s also important to understand that building WordPress themes is nowhere near as simple in 2019 as it was in 2005 when I started hacking away. The code is much more complex. It’s not quite as easy for a new user to piece together something fun as it once was. Unless you have a theme or plugin that allows you to do this with simple drag-and-drop or similar tools, users have little control over their own sites. And, that’s why the Gutenberg project is so revolutionary. Its mission is to put the power back in the hands of the people.

Theme authors need to evolve. They will need to find a way to balance good design principles with the insane amount of freedom users will have. There’s nothing stopping designers from making sure the Bieber screengrab looks more presentable.

Are WordPress Themes Dead?

No. But, the theme landscape will certainly change and not for the first time. We need not look at that as a bad thing.

Those hobbyists who like to tinker with their site, they will once again have power that was so long ago lost to more advanced code.

There will also be sub-communities within the WordPress landscape. Some people will want something more akin to classic WordPress. Others will want a simple blog handled with Markdown (side note: I’m one of those people, and Gutenberg actually handles pasting from Markdown well). Plugins will be built to cater to every user’s needs. Themes will exist for different types of users. Client builds and enterprise solutions that look nothing like core WordPress aren’t going anywhere.

There’s still a long road ahead. Theme authors need to be more involved with the development of Gutenberg as these features make their way into the plugin and eventually into WordPress. Otherwise, they’ll risk losing the opportunity to help shape the future theme landscape.

Truth be told, I’m not sure what themes will look like in a few years. I have a horrible track record with predictions. However, I think it’s safe to say that there’ll be a place for designers.

I’m excited because I feel like it will bring back the potential for users to have the control they once had and more.

WPTavern: Rich Reviews Plugin Discontinued after Vulnerabilities Exploited in the Wild

Wordpress Planet - Fri, 09/27/2019 - 18:25

After tracking exploits of a zero day XSS vulnerability in the Rich Reviews plugin for WordPress, Wordfence is recommending that users remove it from their websites. The company estimates that there are 16,000 active installations vulnerable to unauthenticated plugin option updates:

Attackers are currently abusing this exploit chain to inject malvertising code into target websites. The malvertising code creates redirects and popup ads. Our team has been tracking this attack campaign since April of this year.

Rich Reviews was removed from the WordPress.org Plugin Directory on March 11, 2019, due to a security issue.

One week ago, a Rich Reviews plugin user reported 3 out of 4 of her sites using the plugin were infected with redirect scripts and that removing the plugin fixed the issue. A digital marketing agency called Nuanced Media, the author of the plugin, responded to the post indicating that a new version would be released within two weeks:

We’ve been working on an overall rewrite of this plugin for a while now, but someone out there apparently wanted us to work faster on it, and decided to exploit our plugin to get some malware out there. We’re now going double-quick on it, and hope to have it back up (and newly cozy and secure) within the next two weeks.

Oddly, there seemed to be no rush to patch the issue that is currently being exploited. Yesterday, less than a week after assuring users that a new version is coming, the company behind the plugin announced that it is discontinuing active support and development on Rich Reviews.

Nuanced Media CEO Ryan Flannagan cited Google’s recent changes to its business review guidelines as the reason for discontinuing its development.

“As part of this update, in the organic search results, Google has decided to remove all merchant review star ratings that businesses display on their own URL,” Flannagan said.

“Based on this information, we have discontinued all active development and support on Rich Reviews. We apologize for any inconvenience.”

The announcement does not include any information about the vulnerability or the recent exploits. Users should assume that no patch is coming to the plugin, since it has been officially discontinued. It’s already not available to potential new users on WordPress.org, but those who have Rich Reviews active on their sites should deactivate it and remove the plugin as soon as possible to avoid getting hacked.

Gin

Drupal Themes - Fri, 09/27/2019 - 12:47

A better Content Editor Experience on top of Claro.

This project is is no attempt to fork Claro in any way. It just serves as an extension on what we currently work on at Unic. Some UX changes which are currently out of scope for Claro and/or some customisations we always deliver for our clients. Basically making our changes publicly available for everyone.

Currently work in progress. More to follow.

govstrap

Drupal Themes - Fri, 09/27/2019 - 00:12

a GovCMS light weight bootstrap base theme

WPTavern: Gatsby Raises $15M, Plans to Invest More Heavily in WordPress and CMS Integrations

Wordpress Planet - Thu, 09/26/2019 - 22:35

Gatsby Inc. CEO Kyle Mathews announced a $15M Series A funding round today, just one year after creating the company with GatsbyJS core contributors. The open source Gatsby project started in 2015 to provide a framework for developers to quickly build websites with React. As the project soared in popularity, Mathews formed a company to fund its ongoing development and further invest in the growing Gatsby ecosystem of products.

This round of funding will enable Gatsby to grow its 35-person team while investing in open source and cloud services that complement the company’s products.

“With Gatsby, we’re striving to create a business model that will drive many millions of dollars of investment in open-source tools and enable people to build the next generation of web experiences,” Mathews said.

At the forefront of the company’s vision is the idea of “reinventing website development.” Gatsby has popularized the concept of a “content mesh,” a platform that provides the infrastructure layer for a decoupled website and reimagines the role of a CMS within this architecture.

Gatsby’s goal of creating more integrations for CMS’s was a big part of Mathews’ funding announcement. Instead of writing off LAMP stack architecture as slow and obsolete, Gatsby is creating bridges to the CMS’s that power a large portion of the web:

Instead of a monolithic CMS powering everything, Gatsby ties together specialized services with a modern development experience and optimized website delivery.

This content mesh empowers developers while preserving content creators’ workflows. It gives developers access to great cloud services without the pain of manual integration.

Web developers from dozens of web CMS communities like WordPress and Drupal are going “headless” and using Gatsby as the presentation layer for their CMS.

We’re forming partnerships with these communities to create seamless integrations between their solutions and Gatsby.

Gatsby will be using some of its funding to invest more heavily in the WordPress ecosystem. The company hired hiring Jason Bahl, creator of the GraphQL for WordPress project, in June, and plans to add more WordPress developers.

“We recently hired someone else to work alongside Jason in developing WPGraphQL (announcement coming soon!) and are currently hiring for several roles on the team,” Mathews told the Tavern.

WordPress powers 34.6% of the top 10 million websites and Matt Mullenweg has previously estimated its ecosystem to be a $10 billion industry. The CMS is showing no signs of decline, and is a market that Gatsby product developers are strategically targeting.

WordPress adopted React as its JavaScript framework in 2017, and built its new Gutenberg editor on top of it. Although some early adopters began digging deeper into React and creating their own products with it, the majority of PHP developers have been slow to move in that direction. Gatsby provides a bridge for those who are just getting started.

“We think that for many web developers, a Gatsby project may be the first time they are using React, GraphQL, webpack or even Node.js,” Mathews said. “And that’s not just the case for WordPress developers – the same can be true for professionals in the Drupal, Rails, or .NET ecosystems.

“It’s our goal to make a framework that empowers developers to use these technologies easily, then dive deeper as they gain more experience. So, instead of taking days to configure webpack for the first time, you can use a Gatsby Theme that connects to WordPress as a data source, and automatically get a blazing fast site. Later, you can learn the innards of the system, and begin customizing Gatsby yourself.”

While Gatsby as a framework enables developers to bypass a lot of the technical and tooling jargon that has made modern development so complex, it is still a framework geared almost exclusively towards developers. Mathews said the company’s vision will continue to focus on enabling developers, not on creating solutions to make Gatsby more accessible to the non-technical crowd.

“We are focused on making Gatsby the best choice for WordPress developers who want a flexible and powerful presentation layer for their headless WordPress sites,” he said. “Non-technical team members or clients will still use WordPress to create and manage content, while the web developers on their team or at the agency they hired get to be productive using the best development tools available.”

Gatsby plans to use the funding to invest $3 million per year in open source, including the core Gatsby project, official plugins, and more learning materials. The funding is also good news for the future of the WPGraphQL project, which should see deeper integration with Gatsby in the near future.

WPTavern: Long-Needed Date/Time Improvements Land in Core

Wordpress Planet - Thu, 09/26/2019 - 16:33

After more than a year and several WordPress updates, an overhaul of the core Date/Time component concluded. WordPress 5.3 will ship with fixes for long-standing bugs and new API functions.

Andrey “Rarst” Savchenko spearheaded this project and worked through most of the issues in his WP Date fork of WordPress. Much of his work toward addressing the problems with this core component goes back further with the initialization of his WPDateTime project.

Diving into the Date/Time component is no small feat. Addressing one issue leads to another. It’s a rabbit hole that few in the community have navigated. Many developers were also unaware of the issues. However, the bugs lingered for years, and users had no working solution for the problems they were facing.

The most common errors were caused by core bugs or developer errors due to compatibility issues, described Savchenko. This would cause user-facing issues such as post scheduling and other time-based operations.

With the release of WordPress 5.3, all existing functions should behave more reliably. Developers working on the component fixed several bugs and updated incorrect inline code documentation for many core functions. Along with the fixes, 5.3 will ship with new Date/Time API functions. The updated API includes unified time zone retrieval, localization, and PHP interoperability functions.

Savchenko called it “the slow descent into madness” when asked of the catalyst for diving into the Date/Time component and its underlying issues. “I started to notice serious bugs in the component from WordPress Stack Exchange questions about them, and the more I looked over years the more clear the dire state of it became to me.”

One of the major problems is the way WordPress handles timestamps. “I actually had to invent the ‘WordPress timestamp’ term,” said Savchenko. “There was no name for it in core development and inline documentation incorrectly called these Unix timestamps before.” WordPress adds a time zone offset to the real Unix timestamp, which causes issues with upstream PHP and external systems.

WordPress timestamps couldn’t be removed from core without breaking backward compatibility. Plugin and theme developers should avoid working with the WordPress timestamp and opt to use the recommended methods outlined in Savchenko’s post.

WordPress date functions were originally written in PHP 4, a version of PHP so long-dead that it’s almost not worth digging up the end-of-life date (it’s 11 years, by the way). PHP 5.2 introduced the PHP DateTime and DateTimeZone classes and has continued receiving improvements over the years. WordPress date functions were never updated to utilize newer standards. The platform’s more recent bump to a minimum of PHP 5.6 also meant that the DateTimeImmutable class introduced in PHP 5.5 would be available. The version bump helped land the new API functions in WordPress 5.3.

Some bugs go as far back as 7 years, such as shorthand formats not working with the core date_i18n() function, which was fixed in WordPress 5.1. With any luck, core may also adopt such features as user-based timezones in the future, which would better handle time differences on WordPress installs with users all over the world.

Gary: Talking with WP&UP

Wordpress Planet - Thu, 09/26/2019 - 04:35

At WordCamp Europe this year, I had the opportunity to chat with the folks at WP&UP, who are doing wonderful work providing mental health support in the WordPress community.

Listen to the podcast, and check out the services that WP&UP provide!

BuddyPress: BuddyPress 5.0.0 Release Candidate 2

Wordpress Planet - Thu, 09/26/2019 - 02:31

Hi!

The second release candidate for BuddyPress 5.0.0 is now available for an ultimate round of testing!

Since the first release candidate, we’ve improved the way BP REST API Controllers are loaded inside BuddyPress component classes.

This is an important milestone as we progress toward the BuddyPress 5.0.0 final release date. “Release Candidate” means that we think the new version is ready for release, but with more than 200,000 active installs, hundreds of BuddyPress plugins and Thousands of WordPress themes, it’s possible something was missed. BuddPress 5.0.0 is scheduled to be released on Monday, September 30, but we need your help to get there—if you haven’t tried 5.0.0 yet, now is the time!

Download and test the 5.0.0-RC2

PS: as usual you alternatively get a copy via our Subversion repository.

A detailed changelog will be part of our official release note, but you can get a quick overview by reading the post about the 5.0.0 Beta1 release.

If you think you’ve found a bug, please let us know reporting it on the support forums and/or on our development tracker.

Thanks in advance for giving this second release candidate a test drive!

Pages