All four are on the Free Plugins page. GPL, plain PHP, each with a readme, nothing phones home, nothing asks for a key.

SWS Site Tag — Google Analytics 4 in one setting

Most “analytics” plugins want an account, a dashboard and an upgrade. This one wants a Measurement ID. It loads Google’s tag on public pages only, and tags logged-in users with an anonymous ID and their role so you can filter your own staff out of reports — or tick one box and not track them at all. That’s it. That’s the plugin.

SWS Live Search for WooCommerce

Amazon-style suggestions as the customer types: products with a thumbnail, price and stock state, matching categories, and matching guides or posts, with keyboard navigation and a “see all results” link. It uses WooCommerce’s own product search so the suggestions match the shop page, makes one cached request per keystroke, and needs no third-party search service. We built it for emaudio.com, where customers search by sub size, ohm rating and kit name; it has replaced a surprising amount of “do you have…” email.

SWS Pre-orders for WooCommerce

Tick “Pre-order” on a product, set a ship date, keep selling. The customer sees Pre-order — ships February 15 instead of the dreaded “Available on backorder”, a badge shows on the shop grid, the date follows the item through the cart, checkout, order and emails, and the order is flagged so the person packing boxes doesn’t ship it early. We wrote it the day a supplier told us the new drivers would be “middle of January, then build time”.

SWS Billing Links — retire the WHMCS Bridge

If you embedded WHMCS in WordPress with a bridge plugin and now want WHMCS to stand on its own — new PHP version, no licence to renew, simpler stack — this keeps every old link working. The bridge’s URLs 301 to the right WHMCS page, and any bridge link still printed by your theme or menus is rewritten on the fly. Install it, flip the switch, deactivate the bridge, and nothing anyone bookmarked breaks.

Why give them away?

Partly because they’re small and it’s the right thing to do with GPL code. Mostly because the plugins aren’t the business — installing, tuning and looking after them is. If you’d rather we set them up on your store, with the abandoned-cart emails designed to match your brand and someone watching the sync, that’s Store Ops. If you’d rather never think about updates, backups and PHP versions again, that’s Site Care. And if you just want the plugins, take them. Tell us if something breaks.

No error. No warning. The site was “up”. It just wasn’t the site we thought we had.

How many caches are between you and your visitor?

On a typical managed WordPress site there are at least four, and they don’t talk to each other:

1. Browser cache on the visitor’s device. You can’t clear it. You can only tell it when things change.
2. CDN / edge cache (Cloudflare and friends). Caches images and scripts for sure; sometimes whole pages if someone turned on “cache everything”.
3. Server-level page cache — NGINX, LiteSpeed or Varnish in front of the web server. Invisible from inside WordPress. Often has no button you can see.
4. WordPress page cache — a plugin writing finished HTML to disk so PHP doesn’t run for every visitor.
5. Object cache — Redis or Memcached holding database results. This one caused a second, stranger bug on the same site: a plugin we activated stayed “active” in the admin while the cached list of active plugins told WordPress not to load it. Nothing ran until the cache was flushed.

Our stale homepage was layer 3. The WordPress cache plugin had already been cleared; the server in front of it hadn’t, and it kept serving a copy it had saved when the WordPress plugin was still running. The only fix was a button in the hosting control panel that no “Clear cache” link inside WordPress ever touched.

Why this is a business problem, not a technical one

Every “we changed the phone number on the website” that a customer later says they didn’t see. Every price update that didn’t take. Every “the site still shows the old promotion” conversation. Caching is the first thing to rule out, and almost nobody does, because it’s invisible unless you know to look at headers and timestamps.

How to check your own site in one minute

• Open your homepage in a private/incognito window and add ?x=1 to the end of the address. If the page with ?x=1 differs from the page without it, something upstream is serving a stale copy.
• View the page source (right-click → View Page Source) and search for the word “cache”. Many cache layers leave a dated comment at the top or bottom.
• Make a small, obvious edit — a word in the footer — and check it from your phone on mobile data five minutes later.

When we take a site onto Site Care the first job is a map of exactly which caches sit in front of it and how each one is cleared — then we clear all of them, in order, every time you ask for a change. Edits go live when you expect them to. That’s the whole job.

Then we read the subjects. “Aloha writing about the price.” “Hello, i am wrote about price for reseller.” “Aloha, i am wrote about your the price for reseller.” Eight submissions. Zero customers. The form was working perfectly, for bots.

Why this matters more than it sounds

Spam in a sales inbox isn’t just annoying. It trains the person reading that inbox to skim and delete. The one real quote request that week — from someone who typed “Information request” and wanted a two-zone system priced — sat in a pile of “Aloha” and was answered late. On a form that feeds a sales team, spam has a conversion cost you never see.

It also tells you something about the site: if bots found the form, they’ve found the login page, the comment endpoint and everything else. The form is just the part you can see.

What we did (and didn’t do)

We did not add a CAPTCHA. Making a 60-year-old homeowner identify traffic lights to ask about an air conditioner is how you lose the lead you were trying to protect.

We added a honeypot: an invisible field that humans never see and never fill in, and that bots fill in every time because they fill in everything. Submissions with that field completed are dropped silently. Real people notice nothing. It took five minutes and cost nothing, and the “Aloha” messages stopped the same day.

Then we fixed the other half of the problem — making sure the real messages arrive and are trusted:

• Form email now goes out through a transactional mail service with a delivery log, so “did they get it?” has an answer.
• Reply-To is set to the customer’s address, so the salesperson hits Reply and it just works.
• The domain got proper SPF and DMARC records so Gmail and Yahoo stop treating its mail as suspicious — our free health check flags this, and most small-business domains fail it.

How to tell if your form has the same problem

1. Open the inbox your form sends to. Count submissions from the last 30 days. Now count the ones that were actually from a person.
2. Submit the form yourself from your phone. Time how long the email takes to arrive. If it doesn’t, you have a bigger problem than spam.
3. Look at the sender address on the email that arrives. If it’s the customer’s address, your host is sending mail as other people’s domains, and it will increasingly end up in spam.

None of this is hard. It’s just nobody’s job — until it is. On a Site Care plan, spam protection, delivery logging and the DNS records are part of month one, and we test the form every month so it stays that way.

Fatal error: Only files produced by the PHP 8.2 or 8.3 ionCube Encoders can run on PHP 8.3. The file …/plugins/whmcs-bridge-sso/sso.init.php has been encoded for PHP 7.1.

Nobody had touched the site. The hosting server’s default PHP version had been bumped from 7.4 to 8.3, and one plugin — a paid “bridge” that embedded our billing system inside WordPress — was shipped as encrypted code compiled for a PHP version that is now five years old. It could not run. So nothing ran.

Why most sites don’t notice

Here is the uncomfortable part: the site looked fine from the outside. A server-level cache in front of WordPress kept serving a copy of the homepage it had saved earlier. Visitors saw a website. Anyone who clicked to a page that wasn’t cached, tried to log in, or submitted a form hit the error. If we hadn’t been working on the site that day, the first person to tell us would have been a customer — or nobody, and the quote requests would just have quietly stopped.

This is the normal failure mode for a small-business website. It doesn’t explode. It rots in a corner nobody looks at, and the cost shows up weeks later as “it’s been quiet lately”.

What fixing it actually involved

1. Setting PHP back to 7.4 in the hosting control panel so the site came back up — a two-minute change, if you know where it lives and that it’s the cause.
2. Recognising that the plugin was the real problem: encrypted, licensed, and the vendor wanted money for the PHP-8 build. We didn’t want to be held hostage by a plugin for a feature we could do without.
3. Writing a small replacement that redirects every old URL the bridge used to serve to the billing system directly — so nothing anyone had bookmarked or linked broke — and retiring the bridge. That replacement is now a free download.
4. Only then, with the obstacle gone, planning the move to PHP 8 properly, because two other plugins were already refusing to update until we did.

Total time: an afternoon. Total cost to a business that didn’t catch it: a day or a week of lost leads, plus whatever it costs to find someone to look at it in a hurry.

The thing that would have prevented it

Not a better plugin. Someone whose job it is to notice. An uptime check that loads an uncached page every minute and texts us when it fails. A record of what PHP version the site runs and which plugins can’t survive an upgrade. A person who reads the hosting company’s “we’re upgrading PHP” email, because the business owner has a business to run and shouldn’t.

That is literally the product we built after this week. Site Care is us doing those boring things every month for a flat fee, so the first you hear about a problem is the email saying it’s already fixed.

Three things to check on your own site today

• What PHP version are you on? WordPress → Tools → Site Health → Info → Server. If it says 7.4 or lower, you are on borrowed time; hosts are retiring it.
• Do you have any encoded or licensed plugins? If a plugin’s folder is full of unreadable files, it will not survive a PHP upgrade unless the vendor ships a new build — and they may charge you for it.
• Would you know within five minutes if your site went down? If the honest answer is “a customer would tell me”, that is the gap.

Many thanks to PR Experts for including us in their list of 59 Top North Carolina Brand Marketing Companies and Startups – The Future of Brand Marketing

Click here to view the complete article: https://pr.expert/59-top-north-carolina-brand-marketing-companies-and-startups-the-future-of-brand-marketing/

Always,

SimpWEB

Online tutor for students – People who are good at math, physics, computer programming or any other knowledge can start up an online tutoring service website for students in need and can work locally and globally. There are two ways to make profit, either via a paid member area or via private online sessions on skype for example and get paid per hour.

Sell on Ebay or Amazon – Selling on amazon or ebay costs less than $100 to start up. In fact, almost all houses contain some unneeded items that can be sold on ebay and amazon. There are also tiny items that cost $2 – $7 to buy as wholesale and sell again in amazon and ebay for high profit, example of which are mobile accessories. Take a big note that selling on eBay and amazon requires searching the market perfectly and do good SEO. It is free to learn it as well.

Drop shipping – Drop shipping business is one of the most interesting e-commerce models. The best part behind drop shipping is that anyone with low budget – $100 or less can start a drop shipping. With drop shipping a seller is not responsible for storing or shipping the items, third party companies called drop shippers or drop shipping companies will store and ship the items. Here are brief tips to start-up a drop shipping business:

1-Decide on the niche and select some items to drop ship. Tools like tearpeak can help to know what sells best.

2-Decide on the platform. ebay platform, amazon or Ecommerce

3-Find suppliers that can drop ship the selected items. The best way is to go to companies that you work with and ask them if they have an API or database of products that can be used to import products into an Ecommerce solution.

To learn more about us and how we can help you with you’re online business goals.