PHP Design Patterns Repository

Package:
PHP Design Patterns Repository
Summary:
Implementation of common design patterns in PHP
Groups:
Design Patterns, Language, PHP 5
Author:
Malik Naik
Description:
This package provides an implementation of common design patterns in PHP...

Read more at https://www.phpclasses.org/package/12353-PHP-Implementation-of-common-design-patterns-in-PHP.html#2022-01-13-21:32:41

Navah Hopkins Launches Navah Hopkins Consulting

Navah Hopkins Consulting

Navah Hopkins, a search industry veteran, has officially launched her consulting business, Navah Hopkins Consulting, LLC. Navah is a a highly sought-after paid media and digital marketing strategist with over a decade of empowering brands and the agencies. In her new consulting firm, she plans on providing Digital marketing strategy, Account audits, SAAS product strategy, and General business strategy.

In the past, Navah has worked for companies like Adzooma, Justuno, Hennessey Digital, and WordStream. I’ve known her for years as one of the world’s best Paid Media specialists, and I’ve seen her speak about paid search and paid media at conferences such as Pubcon and State of Search.

Navah has a passion for innovation, fueled by a hybrid of strategic partnerships, data analysis, and consumer engagement. She loves connecting people who can mutually benefit each other, leveraging innovation to solve socioeconomic issues, and maintaining bottom line thinking with an ethics driven perspective.

Navah Hopkins Consulting can help you with your paid media:

  • Google Search Ads
  • Google Display Ads
  • Google Shopping
  • Google Discover Campaigns
  • Google Local Service Ads
  • Youtube
  • Microsoft Search Ads
  • Microsoft Audience Network
  • Facebook Ads
  • Instagram Ads
  • LinkedIn Ads

Welcome to the consulting world, Navah. I am sure you’re love working for yourself; I left the “agency world” back in 2016, and totally enjoy it. I’m sure you will, too.

Perusing the Digital Junk of a Web Designer

If you’re not sure how long you’ve been in the web design industry, take a look at your data. It says a lot about who you are and the things you’ve done.

For someone who started in the mid-1990s, my data archive has volumes to say. From sloppily hand-coded HTML documents to complex (and still sloppy) PHP, the files run the gamut of design fads and of-the-moment technology.

Much of it comes from a time before cloud storage made it easy to take our files from device to device. Moving to a new computer meant creating backups on physical media (CDs, DVDs, external drives, and magnetic tapes). This was necessary – because you never knew when you’d need that super-cool piece of clipart again.

Just for kicks, I decided to do some dumpster diving (er, treasure hunting). I combed through a portion of the digital junk I’ve accumulated over the years. What did I find? What does it all mean? Let’s find out!

Legacy Tools

I have a habit of hanging onto various apps and scripts that were helpful at one time. They might have performed advanced (relative to their time) functions or simply made a monotonous task a bit easier.

Some remain useful, while others gather virtual dust. Among the highlights:

FormToEmail-Pro
This PHP form processing script included the ability to set required fields and a rudimentary CAPTCHA system. All of the settings were contained within a single file. The version date is 2010, so probably not safe to use these days.

NoteTab Pro
An old-school text editor with tons of useful features. The app makes short work of tasks such as stripping HTML tags, changing text case and complex search-and-replace scenarios across multiple files. It was one of the first tools I used that featured code highlighting.

I like this one so much that I still use it. The version I run is from 2014, but the oldest installer on my drive dates back to 2004. And you can still download it.

Eye Candy
I first started using this suite of Photoshop filters back in the 1990s. They allow you to create all manner of interesting special effects – which could be a good or a bad thing. I’ll admit to crafting some fairly obnoxious graphics with it. 😳

The product still exists and has survived despite a company rebrand. It’s installed on my system but doesn’t see quite as much usage as it did back in the day.

HTML Font and Body Tag Wizard
Before WYSIWYG tools were all the rage, this tiny app provided helpful bits of code. I particularly loved it for finding hexadecimal color codes and ASCII characters. This one is long gone, but not forgotten.

What It Says About Web Design
Outside of code editors, tools aimed at web designers tend to be very niche. And that hasn’t changed much over the years.

Perhaps the biggest shift is in how they are packaged. Many functions that were once covered by standalone apps are now web-based. That allows us to use them anywhere and on any device.

And those one-off scripts are now available via content management system (CMS) plugins. They’ve also been given a GUI, which is a lot more convenient than hacking away at code.

Eye Candy Photoshop Filters

Lots of Fonts and Assorted Digital Assets

In the early days of web design, digital assets like fonts and artwork were sold on physical media. Purchase a collection and you’d be swimming in items that are laughable when compared to what’s available today.

Corel was a big player in this market. Their products were fun because they also came with a reference book. Flip through its pages and, when you saw something of interest, the book would direct you to the disc where it could be found. I guess you could say it was an early way to filter results. 😄

I copied every one of the available fonts – all 1,800+ of them – into a folder. While there are a few classic styles included, most look like they came straight out of a 1990s toy catalog.

Then there are the thousands of icons, Photoshop brushes, textures, shapes, and vector images. When was the last time any of these items were used in a project? Let’s just say that it’s been a while!

What It Says About Web Design
The theme here is how over-the-top web design used to be. Before CSS became the powerhouse it is now, intense visuals were often used to make an impact.

Creating elaborate graphics was a common practice. Looking through older sites, you’ll often find busy backgrounds and futuristic banners. And since web typography was quite limited, designers tended to throw every crazy font they could into a project.

The results were mixed. Even if a website looked pleasing to the eye, it could lack basic legibility. Not to mention little-to-no accessibility features. Thank goodness for the shift towards minimalism.

A book of font styles.

Projects That Fizzled

Not every project is worthy of being listed in your portfolio. Some don’t reflect the types of clients you’re looking for. Others may never even make it to launch.

After spending a quarter-century (yikes!) in this industry, I wasn’t surprised to find a number of these projects in the archives. There are dozens of sites that no longer exist or were nothing more than concepts.

Among the items that stood out was my personal site, circa 1999 (coincidentally, the same year I started freelancing). The design very much reflected the technology of the time. It was built with HTML and used table layouts. And it measured a tiny 602 pixels in width – nearly responsive without even trying.

Finding this site was bittersweet, as I used to take pride in having a personal presence on the web. But time marches on, and there’s not enough of it to prioritize that type of project. Alas, it sits in cold storage with the others.

What It Says About Web Design
Being a web designer is an exercise in patience. Sometimes, you need to experience projects that don’t work out to learn from them. It makes you better in the long run.

I can attest to that, as the number of projects in this category has dwindled in recent years. Perhaps it has something to do with the maturity of the web. But it could also be a result of being a little picky about the clients I work with.

That’s the result of putting what you’ve learned into action.

A screen capture of the author's personal website, circa 1999.

The History of a Web Designer, as Told by Files

Finally, hoarding files has paid off! All joking aside, digging through the past was a fun exercise. It’s something I would recommend to any web professional who has a few years’ worth of archives saved up.

You’ll likely find some surprises, along with items you’d forgotten about. Most of all, you’ll see how far both you and the web have come over time. It can serve as a comforting reminder as you move forward in your career.

The post Perusing the Digital Junk of a Web Designer appeared first on Speckyboy Design Magazine.

Are Low-Cost WordPress Projects Worth Your Time?

If you’re a freelancer looking for new clients, you’ll likely find plenty of opportunities to take on low-cost WordPress projects. But pairing the term “low-cost” with WordPress seems like an oxymoron.

Sure, it may accurately describe what a client is willing to pay. That doesn’t speak to the challenges involved, though. These projects always tend to be more than meets the eye.

I’ve spent over a decade working in the WordPress space. And I can’t recall a single project that didn’t involve multiple revisions and at least some customization. Even a website that uses a third-party theme and a few select plugins will need some tweaks. This process encompasses projects at every pricing level.

It begs the question: are low-cost WordPress projects worth your time? The answer depends on what exactly you’re looking to gain.

Don’t Expect to Improve Your Financial Standing

Building websites at a discounted rate rarely ends up making you rich – at least not at the lower end of the scale. And, despite its massive ecosystem, utilizing WordPress in these projects only complicates the matter.

The theory behind low pricing is often based on two things:

  • Working on a higher volume of projects;
  • Offering lucrative upsells;

This clashes with the typical WordPress site. There are an almost endless array of themes and plugins to choose from (we’re not including from-scratch custom work, as that’s likely beyond a small budget). Thus, there are so many potential tweaks a client can ask for.

To turn a good profit, it would seem that a designer needs to be ultra-specific regarding what’s included in their baseline deal. Otherwise, the line between included services and upsells can become blurred.

Not to mention the time involved in the build and revision processes. There may not be enough hours in the day to work on the volume of projects necessary to earn a healthy sum.

A piggy bank with coins.

You’ll Learn Some Things about WordPress

Every project – regardless of price – represents an opportunity to learn. Putting a website together on a shoestring budget provides its own unique experience in this area.

Because we’re talking about low-cost projects, the chance to dive into custom code will likely be limited. That is unless you’re approaching things with the sole purpose of learning.

Even if that’s not the case, the knowledge you gain can still be valuable. For example, you’ll have lots of one-on-one time with the WordPress back end. That provides a foundation of how the dashboard works, where various settings reside, and plenty of practice with the Gutenberg block editor.

Then there’s also a great benefit to learning about WordPress plugins. Building these sorts of websites often means relying on third-party code. You’ll have a chance to find niche plugins that you can use both now and in the future. That’s a great resource to have at your disposal as you move through various projects.

In addition, you’ll also be able to identify pain points that arise during the build process. Knowing, for instance, what a particular theme can and can’t do has value. The same goes for plugins and WordPress itself.

A person writes in a notebook.

An Opportunity to Build Your Portfolio

If your portfolio is a little on the thin side, taking on smaller sites can be an effective way to beef it up. This is particularly important when you’re in the beginning stages of your career, when new clients may be hard to find.

However, you’ll want to approach this area with some caution. Adding low-budget WordPress projects to your portfolio can be a double-edged sword.

On one side, proudly displaying your work can add legitimacy to your brand. A prospective client will see what you’ve done and have confidence that you are qualified.

The downside is in how those projects are perceived. If a specific website looks low-budget, you may set yourself up to be typecast. Organizations may see you as someone they can turn to for cheap pricing, which may not be ideal for your long-term growth.

Therefore, it’s best to use some discretion as to which projects make it into your portfolio. Include those that have something unique to offer, but perhaps leave out the ones that are of a lower level.

A woman works at a computer.

Know What You’re Getting Into

The decision of whether or not to work on low-cost WordPress websites is a very personal one. So much depends on where you are in your career and what you’re looking to achieve.

Veteran designers and developers may not have much reason to play in this space. Although, some may see it as a way to fill in some gaps in their schedule or help out a friend.

If you’re just starting, there is a lot of value in building a cheap website or two. The more you can work with WordPress, the more proficient you’ll become with the content management system (CMS). This experience can pay off down the road.

Besides, very few of us start out working on high-end projects. The natural path tends to be starting small and moving up over time. This can better prepare you for the responsibilities and advanced knowledge required to work with larger organizations.

However, it’s important to know what you’re getting into. If you’re comfortable with the limitations that come along with low-cost projects, then don’t be afraid to jump in.

The post Are Low-Cost WordPress Projects Worth Your Time? appeared first on Speckyboy Design Magazine.

CakePHP Pagination Helper Trait

Package:
CakePHP Pagination Helper Trait
Summary:
Add pagination to listings generated by CakePHP
Groups:
Databases, Design Patterns, Libraries, PHP 5, Traits
Author:
Roman Kozin
Description:
This package can add pagination to listings generated by CakePHP...

Read more at https://www.phpclasses.org/package/12351-PHP-Add-pagination-to-listings-generated-by-CakePHP.html#2022-01-11-20:00:25

cakephp3-json-pagination

Package:
cakephp3-json-pagination
Summary:
Add pagination to listings generated by CakePHP
Groups:
Databases, Design Patterns, Libraries, PHP 5, Traits
Author:
Roman Kozin
Description:
This package can add pagination to listings generated by CakePHP...

Read more at https://www.phpclasses.org/package/12351-PHP-Add-pagination-to-listings-generated-by-CakePHP.html#2022-01-11-20:00:25

WordPress 5.9 RC 2

The second Release Candidate (RC2) for WordPress 5.9 is now available! 

“Release Candidate” means the new version of the software is ready for release. It helps the community check that nothing is missed, given the thousands of plugins and themes and differences in how millions of people use the software.

Thank you to everyone who has contributed thus far towards testing and filing bugs to help make WordPress 5.9 a great release. WordPress 5.9 is slated for release in just two weeks on January 25, 2022. There’s still time to help! Since RC1 was released, six bugs have been found and fixed. There were 13 bug fixes backported from Gutenberg.

Testing the release

You can test the WordPress 5.9 release candidate in three ways:

Option 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).

Option 2: Direct download the beta version here (zip).

Option 3: When using WP-CLI to upgrade from Beta 1, 2, 3, 4, or RC1, on a case-insensitive filesystem, please use the following command sequence:

Command One:

wp core update --version=5.9-RC2

Command Two:

wp core update --version=5.9-RC2 --force

Your help to test the second Release Candidate is vital: the more testing that happens, the more stable the release, and the better the experience for users and developers—and the entire WordPress community.

Thank you to all of the contributors who tested the RC1 release and gave feedback. Testing for bugs is not just a critical part of polishing every release, it is also a great way to contribute to WordPress.

How to Help

Help test WordPress 5.9 features – a guide to how you can take part.

Can you write in another language other than English? You can help translate WordPress into more than 100 languages! Release Candidate 1 marked the hard string freeze point of the 5.9 release schedule. Thanks to every locale that is already involved with translations.

Developers and those interested in more of the background to the features can find more in the Field Notes. More developer notes will be added as the release progresses to its final stage. You can also follow the 5.9 development cycle and timeline.

If you think you have found a bug, you can post the details to the Alpha/Beta area in the support forums.

 If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac, where you can also check the issue against a list of known bugs.

Props to: @psykro and @webcommsat, and @hellofromtonya, @audrasjb, @cbringmann and @marybaum for final review.

Xdebug Update: December 2021

Xdebug Update: December 2021

In this monthly update I explain what happened with Xdebug development in this past month. These will be published on the first Tuesday after the 5th of each month.

Patreon and GitHub supporters will get it earlier, around the first of each month.

You can become a patron or support me through GitHub Sponsors. I am currently 46% towards my $2,500 per month goal. If you are leading a team or company, then it is also possible to support Xdebug through a subscription.

In December, I worked on Xdebug directly for only about 26 hours, with funding being around 21 hours. Please become a supporter of Xdebug through Patreon or GitHub.

Xdebug 3.1 and further

On the first of the month, I released Xdebug 3.1.2.

It addresses a few crash bugs related to PHP 8.1 fibers, a crash bug when Xdebug can't write a profiler file, and an issue with Xdebug's var_dump() not using the magic __debugInfo method.

The full list of changes can be found on the updates page on the Xdebug website.

Since Xdebug 3.1.2 I have fixed a few more bugs, which are not yet in a released version. One fix pertains to the debugger generating not-well-formed XML, and another one improves performance with long strings in the debugger.

I spend most of my time in December to investigate issues that have not yet been solved. One of them turned to be a change in PHP behaviour between PHP 8.0 and 8.1. In PHP 8.0 and earlier, the $_GLOBALS[] superglobal also had a key GLOBALS, which PHP 8.1 no longer has. PhpStorm was reading values for its watch feature, from the GLOBALS context, but also added the extra (unnecessary) GLOBALS array element to read out the real variables. Fixing this in Xdebug is complex, so hopefully this will be addressed in the next version of PhpStorm itself.

The second issue turned out to be an issue with PHP-FPM, which is not strictly following PHP's processing model. This can cause a discrepancy between PHP-FPM's control and worker processes, where they do not agree what the value of the xdebug.mode INI setting is. Ideally this should get fixed in PHP-FPM, but there are further issues that both PHP-FPM and Xdebug probably need changes for.

Xdebug Videos

I did not create any new Xdebug videos this month on my YouTube channel. But I am working on a more thought out set of instructional videos. Stay Tuned!

If you would like to suggest a topic for a 5 to 15 minute long video, feel free to request them through this Google Form.

Truncated by Planet PHP, read more at the original (another 582 bytes)

Powered by Gewgley