Roastidio.us Tagged with admin

How to Disable All Automatic Updates (WordPress Core, Plugins, and Themes)

Fri, 02 Oct 2026 15:26:20 +0000

Everyone has their own preference when it comes to automatic updates. Many folks like the idea of saving time and not having to “do” anything when updates are available. The problem is that updates don’t always go as planned. Unexpected things happen, conflicts, bugs, etc. Best-case scenario you save some time. Worst-case scenario your site goes down. Personally, I prefer to disable automatic updates for all the things: WordPress core, plugins, and themes. To do it, I use the following code snippets..

Disable automatic updates via constants
Disable automatic updates via filter hooks

Disable automatic updates via constants

This is the code snippet that I add to every site to turn off ALL automatic updates. Added via the wp-config.php file, just before the line that says, “That’s all, stop editing! Happy blogging.” Here is the magic code:

// Disable auto-updates for EVERYTHING
define('AUTOMATIC_UPDATER_DISABLED', true);

// Disable auto-updates for WP CORE
define('WP_AUTO_UPDATE_CORE', false);

// Disable auto-updates for PLUGINS & THEMES
define('CORE_UPGRADE_SKIP_NEW_BUNDLED', true);

Here we define three constants. The first constant disables all automatic updates. So technically that’s all you need. The second constant disables auto-updates for the WordPress core. The third constant disables auto-updates for plugins and themes. It’s as simple as that, and it just works.

Notes

By changing the values of the constants, you can define other configurations for automatic updates. For example, you can enable core updates while disabling plugin/theme updates and vice versa. In fact, the WP_AUTO_UPDATE_CORE constant may be one of three possible values:

true – All updates (major, minor, and dev) are enabled
false – All updates (major, minor, and dev) are disabled
'minor' – Only minor updates are enabled (major & dev are disabled)

The other two constants, AUTOMATIC_UPDATER_DISABLED and CORE_UPGRADE_SKIP_NEW_BUNDLED, are strictly boolean (true or false).

Also note that “dev” updates only happen on sites running a development version of WordPress.

Disable automatic updates via filter hooks

Instead of using constants, it’s possible to configure automatic updates using filter hooks. Going the “filter” route is somewhat more flexible. Best advice is to go with constants via wp-config.php if you simply want to disable automatic updates. For alternate configurations, using filters gives you more granular control over each aspect of the update process.

Note: The code snippets below can be added via must-use plugin or custom code. Do NOT add any of the following code directly to wp-config.php.

Here are the filters that may be used to configure automatic updates:

// Disable auto-updates for EVERYTHING
add_filter('automatic_updater_disabled', '__return_false');

// Disable auto-updates for WP CORE
add_filter('auto_update_core', '__return_false');

// Disable auto-updates for PLUGINS
add_filter('auto_update_plugin', '__return_false');

// Disable auto-updates for THEMES
add_filter('auto_update_theme', '__return_false');

// Disable auto-updates for TRANSLATIONS
add_filter('auto_update_translation', '__return_false');

As written here, these filters all return false, which disables their respective auto-update feature. To instead enable any update feature, simply replace __return_false with __return_true.

Notes

The auto_update_core filter disables all core-related updates: major, minor, and dev. For more granular control, you can use the following alternate filters:

allow_dev_auto_core_updates
allow_minor_auto_core_updates
allow_major_auto_core_updates

These filters do exactly what their names imply. For more details, check out this WordPress article. As explained there, even when disabling auto-updates using auto_update_core and related filters, WordPress will continue making HTTP requests to the update endpoints:

https://api.wordpress.org/core/version-check/...
https://api.wordpress.org/plugins/update-check/...
https://api.wordpress.org/themes/update-check/...

If you want to stop WordPress from checking for updates, you can add the following code via must-use plugin, regular plugin, or via functions.php:

// Stop HTTP requests checking for updates
remove_action('admin_init', '_maybe_update_core');
remove_action('admin_init', '_maybe_update_plugins');
remove_action('admin_init', '_maybe_update_themes');

That’s all for now, I hope this tutorial helps you in your WordPress adventures :)

Codeless Way to Include External Directory in Sitemap | Digging Into WordPress

Fri, 02 Oct 2026 15:26:20 +0000

As of version 5.5, WordPress automatically generates an XML sitemap for your site’s content. The sitemap benefits your site by providing a simple “map” of all posts, pages, categories, tags, and more. This is useful for bots and humans, and is considered beneficial for SEO and even GEO. Even better, WordPress makes it easy to customize your sitemap as desired. For example, if you want to include or exclude certain pages, or even disable the WP sitemap completely, there are programmatic techniques (i.e., code snippets) for making it happen.

Add a directory without code

Now that we’re on the same page, so to speak. This quick DigWP tutorial explains how to add an external directory to the auto-generated WordPress sitemap. And by “external”, I’m referring to any directory that is not under the purview of WordPress (based on its URL). More specifically, any directory or folder that you add manually to your site’s files.

Step 1: Requirements

Okay let’s dig into it. For this non-code trick to work, the main requirement is that your site has permalinks enabled (via the WordPress General settings ▸ Permalinks). So instead of query-string-based URLs:

https://example.com/?p=123

..your site’s rocking keyword-rich “pretty” URLs:

https://example.com/ai-will-replace-the-internet/

Other than permalinks, there are two other caveats:

Directory name consists of alphanumeric, underscores, and hyphens
Directory location is within the site’s root directory

These requirements are explained further as we continue with the tutorial..

Step 2: Add a directory

Next add a directory to your WordPress site. Anywhere in the root directory of your site. For example, when I moved my shapeSpace WordPress theme from its own domain to Perishable Press, I added a directory named /shapespace/ to the site’s root directory. So the resulting directory path is this:

https://perishablepress.com/shapespace/

Important: for this non-code technique to work, the folder name must consist of only alphanumeric characters, underscores, and/or hyphens.

Step 3: Add new Page

Next, visit the WordPress Admin Area and create a new page (via Pages ▸ Add Page). Make sure that the page has a URL/permalink slug that matches your directory path. So continuing with the /shapespace/ directory example, we would add a new page that is named shapespace, which results in a permalink URL that matches the external directory. So both the directory and the newly added page have the same URL:

https://perishablepress.com/shapespace/

That’s all there is to it. Once you publish the new page, WordPress will do its thing and automatically add the new URL to your XML sitemap.

Check it out..

As long as the external directory and WP Page have the same URL, your WordPress sitemap will include a link to your directory. And when you (or anyone, anything) follows the link, they will be taken to the directory, not the WordPress Page. To get a better idea of how it works, check out the pages sitemap at Perishable Press, and follow the link to the external /shapespace/ directory. Instead of pointing to the blank WP Page, the sitemap link points to the shapeSpace directory, which serves the shapeSpace homepage.

A few final notes

This “codeless” way of adding directories to the WP sitemap works seamlessly. The new URL appears in your site’s local search results and links to the external directory (not the blank WP Page). That means the contents of the WP Page never are displayed anywhere on the front end of your site. So you can add a note or whatever reminding your future self why this otherwise empty page exists ;)

Note: This no-code technique works whether WordPress is installed in the root directory or subdirectory. Just FYI.

And of course, the main benefit of adding a directory to your sitemap is so the search engines can find it, pick it up, and include it in the search results. And that’s just smart SEO.

What about adding files?

Does this tricksy non-code technique also work with external files (instead of directories)? Not really, because of the limitations in how permalinks are formatted. For example, permalinks end with a forward slash /, file names do not. Also special characters like periods/dots that are included in file names are not included in permalinks. So if you add an external file named external-file.html, the closest you can get with a static page name is /external-file-html/, which won’t work for the sitemap trick.

Fortunately you always can add files and directories and just about anything using the Sitemaps API now included in WordPress core :)

Plan launches, events, and tests with clearer and more granular controls in Rollouts

Mon, 28 Sep 2026 20:36:02 +0000

Rollouts has a redesigned setup experience that makes it easier to plan a launch, run a temporary event, or test changes to your store.

Reflect your intent: Choose the timing and traffic percentage for your rollout. Rollout settings will adjust to reflect your intent as a launch, temporary event, or an experiment.
Combine multiple changes: Make changes to your theme, checkout and customer account pages in a single rollout.
Understand your audience: See what percentage of traffic your rollout reaches and how it’s split between test versions.
Review conflicts: See conflicting settings directly in the setup flow so you can address them earlier.

Learn more about the new Rollouts configuration in our help documentation.

The Plural Of Beef

Mon, 28 Sep 2026 04:49:42 +0000

Me: Hey, sorry to bother you.

Grace Draven: No problem. What’s up?

Me: Do you know what chevon is?

Grace: … No. Never heard that before. It sounds French. What is it?

Me: Goat meat.

Grace: Huh.

Me: Apparently, it’s chevon, except if you are in India or Pakistan where it is called mutton for cultural reasons. You are the foodiest person I know, so I figured if you didn’t know it, nobody else would.

Grace: It says here “Chevon is a coined culinary word created in 1922 by a trade association as a blend of the French word chèvre (goat) and the ending of mutton.”

Me: Yep.

Grace: How are you?

Me: grunt.

Grace: You can do it. It will be okay.

I am not quite sure I can do it, actually. We are crash editing Maggie 2 to get it under the deadline, so it doesn’t have to be bumped back. It’s been 12 hour days back to back for a month now. It’s a very long book. I broke out the Fortnum & Mason Christmas tea that Mod R sends me for Christmas. And I put honey in it, which I cannot do because prediabetes.

Parallel to that, we are finishing up the vellum orders. As of right now, we have 267 orders to go. The end is in sight. We had numerous printer-related delays, which will not happen again, because 3,000 orders is too many. From now on, we will do small merch drops of 1,000 sets at a time. When they sell out, they sell out.

Behind on everything otherwise. Hoping to get to some kind of place once the edit is done. Also I almost got the flu. It’s going around and I had a couple of miserable days with some fever, but I think I might have fought it off. Knock on wood, cannot get sick right now.

Thank you for your patience with us.

PS. The plural of beef is beeves.

PPS. ::Channeling Maggie from Maggie 2:: And one more thing: Guys, if your vellum arrived damaged, let us know. We will replace. Please email to the store address: store@ilona-andrews.com. Mod R cannot help you.

PPPS: Experts found, thank you!

The post The Plural Of Beef first appeared on ILONA ANDREWS.

AIforce: Salesforce’s New AI Interface Layer for Slack, Claude, and Lightning

Sat, 19 Sep 2026 19:44:36 +0000

Slackforce, Claudeforce, and Agentforce Coworker aren't three separate launches. They're three expressions of the same shift. Salesforce's context, permissions, and business logic no longer stop at the edge of its own UI.

Slackforce puts that context into shared, live team surfaces. Claudeforce puts it into a reasoning layer built for individual sellers. Agentforce Coworker keeps it running natively where millions of users already work every day.

For admins and developers, years of Salesforce data, workflows, and configuration are already sitting there, ready to use. That value no longer requires a dashboard to reach. AIforce is Salesforce's bet that describing what you need will replace navigating to find it. That bet plays out across every surface your team already uses.

The post AIforce: Salesforce’s New AI Interface Layer for Slack, Claude, and Lightning appeared first on Salesforce Break.

Dreamforce 2026: One Message You Missed Is The Real Game Changer

Sat, 19 Sep 2026 19:44:36 +0000

Marc Benioff opened Dreamforce 2026 on September 15 with a packed keynote hall: 10,000 people in the room and 10 million more watching on Salesforce+. Salesforce counted 53,000 total attendees at Moscone Center this year, spread across more than 1,600 sessions. Here's what admins and practitioners need to know from the opening keynote.

The post Dreamforce 2026: One Message You Missed Is The Real Game Changer appeared first on Salesforce Break.

Salesforce Timezone Offset: A Native Flow Alternative to Apex

Sat, 19 Sep 2026 19:44:36 +0000

Every system time field in Salesforce is stored in GMT. That part is simple. What complicates things is everything layered on top of it. An org has its own timezone setting. A user can have a different timezone than the org. Salesforce uses both settings to decide how timestamps display on records and transactions. Installed …

The post Salesforce Timezone Offset: A Native Flow Alternative to Apex appeared first on Salesforce Break.

SOQL Basics for Salesforce Admins

Sat, 19 Sep 2026 19:44:36 +0000

If you have spent any amount of time in the Salesforce ecosystem as an admin, you know this exact routine: A stakeholder asks for a dataset. You build a custom report type, drag and drop fields, apply filters, and hit Export. Then, because Salesforce reports cannot easily pull data across non-related branches or cross-reference two …

The post SOQL Basics for Salesforce Admins appeared first on Salesforce Break.

Salesforce Rebuilds Licensing Tiers and Adds Agentforce

Sat, 19 Sep 2026 19:44:36 +0000

Before you assume any tier covers your team's needs, map the feature list against what you actually use. A "Max" upgrade sounds like an easy yes, especially at unchanged pricing, but the value only lands if your org uses the tools that got added.

We'd also treat Salesforce's value percentages as vendor claims rather than settled fact. They're useful directional signals, not numbers to build a budget justification around without your own math behind them.

Industry Edition pricing isn't final yet. Salesforce says that lands later this fall, so orgs in regulated industries should hold off on locking in a decision until that detail arrives.

The post Salesforce Rebuilds Licensing Tiers and Adds Agentforce appeared first on Salesforce Break.

Claudeforce Explained: Salesforce and Anthropic's New AI-CRM Partnership - Salesforce Break

Sat, 19 Sep 2026 19:44:36 +0000

Salesforce and Anthropic announced Claudeforce on August 26, 2026, during Salesforce’s Q2 FY27 earnings call. Claudeforce brings Claude’s reasoning together with Salesforce’s data, workflows, business logic, and governance, and makes it strategically accessible from inside Claude itself.

Many people lean on AI and LLMs to get through their workday. Sellers are turning to Claude for research, drafting, and quick answers, for example. Salesforce saw an opportunity and decided to meet the users there instead of asking them to come back to Salesforce. Partnering with Anthropic let Salesforce bring its data and rules into a tool people already use every day, rather than building another interface for sellers to learn.

Claudeforce launches with 37 skills built for Sales specifically, and only works within a user’s existing Salesforce permissions, so access depends on being both a Salesforce user and someone with sales-team access today.

What Salesforce in Claude Actually Does

Traditional software puts the burden on the seller. Open the account. Click into the history. Piece together the story before you can act. Salesforce in Claude makes it easier. Sellers can ask Claude about a deal, a pipeline, or an account, and Claude reasons across Salesforce, Slack, and email to answer and act, without the seller navigating between screens.

The 37 sales skills cover the seller workflow end to end: meeting prep, deal health checks, pipeline reviews, and more. Salesforce and Anthropic built these skills specifically for Claude’s reasoning and generative UI. They are not generic prompts wrapped around an API call.

According to Salesforce, one use case could be an onboarding flow that reads a seller’s Salesforce, Slack, and connected data to build a tailored dashboard automatically, generated live inside Claude.

Image source: https://www.salesforce.com/claudeforce/

The Underlying Infrastructure: Headless 360 and MCP

Salesforce in Claude runs on AIforce, Salesforce’s trusted enterprise harness. AIforce brings business data and workflows to any agent through MCP servers, APIs, and CLI tools. It builds on the Headless 360 architecture Salesforce introduced at TDX 2026, exposing data, workflows, agents, and governance through MCP. No custom integration work required.

Image source: https://developer.salesforce.com/blogs/2026/05/headless-360-what-it-means-for-developers

The mechanism is the same one we’ve written about since TDX: MCP turns Salesforce capabilities that used to require logging in and clicking through screens into something an agent can reach directly, wherever the seller is working.

Governance in Salesforce Gets Reused

This is the part admins will care about most: Salesforce in Claude runs through your existing Salesforce permissions and business rules. Claude sees only what a given user is authorized to see, and can only do what that user is authorized to do.

There’s no new permissions model to stand up and no per-user configuration. An admin connects Salesforce in Claude once, and it works for the whole team from day one.

Write actions come with configurable controls. You decide whether Claude checks with you before sending an external email, or sends it once you trust the workflow. When Claude updates a record, it changes only the field it said it would change.

Salesforce and Anthropic say they’re continuing to build additional enterprise controls together, including data residency and access controls, plus automated review meant to catch problems before they reach customers.

Should Salesforce Admins Care About Claudeforce?

Salesforce in Claude is live today for select pilot customers. Salesforce and Anthropic plan an open beta starting in September 2026. The initial release focuses on Sales skills, with plans to expand into other teams in the months following. If you’re a Salesforce admin, the governance model is the detail to watch. Claudeforce doesn’t ask you to build a second permissions layer or trust a black box. It routes everything through the rules you already enforce.

Image source: https://www.salesforce.com/claudeforce/

If you’re a seller, the pitch is fewer clicks and less manual digging. Whether that holds up in daily use is the question worth asking as the open beta rolls out in September.

We’ll track Claudeforce through pilot feedback and the open beta launch, and follow up with hands-on coverage once broader access opens.

What do you think, admins, does Caludeforce news fill you with excitement or anxiety?

Explore related content:

Why Headless Architecture Is the Foundation Salesforce Teams Need

8 Dreamforce 2026 Sessions for Every Admin’s Agenda

Agentforce Agent Flow Action Best Practices

A new look for the Shopify admin

Wed, 16 Sep 2026 06:46:34 +0000

On September 15th, we began rolling out a new look for the Shopify admin: new color, type, spacing, and icons across every page, inside a new frame.

Search, notifications, and the store picker have moved into the side navigation, which collapses for more room on the page. Sidekick has moved from a side panel to a floating chat at the bottom of every page, so it’s in reach from wherever merchants are working.

The new look rolls out gradually and will arrive to your admin on its own with no setup needed.

Learn more about the admins new look in Shopify Help Center.

Multi-currency payouts now available in Australia and France

Sat, 12 Sep 2026 22:09:57 +0000

We've expanded Multi-Currency Payouts for eligible Shopify Payments merchants to Australia and France.

Merchants in Australia can now receive payouts in 13 currencies: AUD, NZD, USD, EUR, GBP, CAD, NOK, SEK, DKK, CHF, JPY, SGD and HKD. All 13 can be paid into an Australian bank account, or you can add an account in the US, New Zealand, the UK, Canada or the eurozone for those currencies.

Merchants in France can now receive payouts in 18 currencies: EUR, AUD, CAD, CHF, CZK, DKK, GBP, HKD, HUF, JPY, NOK, NZD, PLN, RON, SEK, SGD, USD and ZAR. EUR remains your default payout currency, and other currencies are paid into additional bank accounts you add.

Multi-currency payouts are available to stores on the Advanced and Shopify Plus plans. More info in help docs

Palomar – a registry of Lean verified mathematics | What's new

Sat, 05 Sep 2026 00:34:42 +0000

In recent months there has been a proliferation of AI-generated proofs of various old and new results, some of which have been formalized in the proof assistant language Lean. However, checking that a given Lean repository actually proves the claimed statement is somewhat non-trivial, especially for an audience which is not expert in the use of Lean: one has to first check that the claimed formal Lean statements have proofs that typecheck, that the proofs do not contain any “cheats” such as adding additional axioms, and that the formal statements also match (in a semantic sense) the informal description of the claimed results.

To help bring some clarity to this situation, I am happy to announce that Palomar registry of Lean verified mathematics, which is an initiative incubated by the Lean FRO and by ICARM, is now open for submissions. I am serving in several roles on this registry, including on the scientific advisory board, together with Jeremy Avigad, Matthew Ballard, Jaume de Dios, Nestor Guillen, Bryna Kra, Kim Morrison, Ravi Vakil, and Akshay Venkatesh.

A detailed motivation for Palomar can be found here, and further information about Palomar can be found here. A zeroth approximation of what Palomar intends to be is the analogue of a preprint server for Lean proofs. More precisely, Palomar (which is named after the astronomical observatory) is a registry of external Github repositories (or more precisely, “snapshots” of such repositories, as represented by a specific Github commit) containing Lean code adhering to the current best practices for such formalizations, in particular containing

A “challenge file” containing a short, human readable description in Lean of the results claimed.
A “solution module” containing an (arbitrarily long) proof of the results claimed in the challenge file.
A “formalization.yaml” file describing the results in informal language, and also containing a number of other relevant metadata and disclosures.

(There are also some additional technical requirements for the repository which I will omit here.) If a snapshot of a repository is submitted to Palomar, it will check both (a) that the solution module typechecks and proves exactly the results claimed in the challenge file, and that (b) the informal description of the result in the formalization.yaml file appears to match the result claimed in the challenge file, and that the repository meets various minimal standards required for a registry entry. The first check (a) is purely mechanical, using the Lean tool Comparator; the second check (b) is non-deterministic, being performed by a large language model. If a repository passes both checks, it can be registered on Palomar. It is worth stressing that the checks in (a) and (b) fall well short of what a proper human peer review of a submission for novelty, interest, and accuracy would give; in particular, Palomar is not a peer-reviewed journal.

The submission process is thorough, but achievable: as a test, I successfully managed to submit my own recent formalization of the proof of Sendov’s conjecture to Palomar, and also plan to submit some older formalizations to the registry soon.

In any event, the registry is now open for formalizations of both old and new results. Submissions (whether human-generated, AI-generated, or some mixture of both) are welcome; please read the (somewhat detailed) instructions here before starting a submission. (I will however note that modern AI agents are quite helpful in assisting with the mechanical details of the submission, though a human review is still strongly recommended.)

Discussion and feedback on Palomar will occur on this Zulip channel.

Bulk staff setup with CSV import

Fri, 04 Sep 2026 20:37:05 +0000

You can now create, suspend, and reactivate staff accounts in bulk by uploading a CSV file in Shopify admin.

This update helps reduce manual setup for larger teams by letting you bulk create admin or POS staff accounts with assigned PINs and suspend or reactivate existing users in one upload.

It’s especially useful for seasonal hiring, store expansion, and fast offboarding, when teams need to make staff changes quickly and accurately.

To use this feature, go to Settings > Users > Import in Shopify Admin. Download the sample CSV template there to get started.

Learn more about importing users in bulk using a CSV file.

Recommended changes to checkout field settings are now available

Fri, 04 Sep 2026 20:37:05 +0000

Eligible stores can now get personalized recommendations for customer information settings from the Checkout settings page in Shopify admin.

These recommendations help you collect more complete customer details at checkout so you can reconnect with past shoppers more effectively and personalize your marketing. New stores already use these recommended settings by default.

Recommendations may include setting customer contact method to email-only, requiring first and last name, or optionally collecting shipping address phone number.

You can review recommendations and apply any changes directly from Checkout settings. Existing store settings won’t change unless you apply the recommendations.

Taxes now recalculate when you change an order's shipping address

Fri, 04 Sep 2026 20:37:05 +0000

Update: Tax rates vary by destination. Previously, the original destination tax stayed on the order even after you updated the shipping address, so your financials and tax reporting could drift out of sync. Now the order reflects the taxes for where it's actually shipping, which keeps your records accurate.

Taxes are recalculated for the new shipping address, and you’ll see a preview of the updated amounts before saving.
If the change creates a payment difference, you'll see it before you save, so you can choose to send an invoice to the customer.

Learn more about editing a shipping address in the Shopify Help Center.

Managed Markets is ending Delivered Duty Unpaid (DDU) support

Fri, 04 Sep 2026 20:37:05 +0000

On August 24, 2026, Shopify Managed Markets will stop supporting delivered duty unpaid (DDU) in every country and region where it supports delivered duty paid (DDP).

What's changing

Markets that use or inherit DDU automatically move to DDP wherever Managed Markets supports it.
Customers in those markets will now pay duties and taxes at checkout, not to the carrier or customs on delivery.

Collecting duties and taxes at checkout helps avoid surprise costs on delivery and makes international shopping more predictable.

What you need to do

If you want your customers to keep paying on delivery, turn off Shopify Managed Markets before August 24, 2026. Otherwise, no action is needed.

Learn more about Managed Markets in the Shopify Help Center.

Shopify Messaging now supports WhatsApp marketing

Fri, 04 Sep 2026 20:37:05 +0000

WhatsApp marketing is now part of Shopify Messaging, helping you serve customers globally and drive sales with another channel to market and promote your business.

Create your WhatsApp campaigns using pre-built templates or your own branded content. Add media from your product catalog, and set up interactive buttons and keyword replies that engage your customers when they click or reply with a keyword. With flexible pricing, you can scale up WhatsApp marketing campaigns during busy seasons and scale down when you need to—only paying for the messages you send.

To learn how to create and send WhatsApp marketing campaigns, visit the Shopify Help Center.

UPS return labels are now available

Fri, 04 Sep 2026 20:37:05 +0000

You can now create UPS return labels from any fulfilled order in your Shopify admin. Select an order, create a return, and choose UPS as the carrier. The label is sent to your customer by email or a shareable link.

You can purchase return labels through Shopify's discounted UPS rates, or you can connect your UPS account to Shopify and create UPS return labels using your own account rates.

You're only charged when the carrier scans the label—unused labels expire after six months at no charge. Available for US domestic orders.

To learn more, visit our Help Center.

Localized address fields are rolling out to checkout and Shopify admin for Brazil, the Philippines, Kuwait, Peru and Panama

Fri, 04 Sep 2026 20:37:05 +0000

Localized address fields are now rolling out for addresses in Brazil, the Philippines, Kuwait, Peru, and Panama. No action is required. These fields are available:

when buyers check out, or save an address in their account profile page
in the admin when you save a customer address to their profile page, or edit an order's shipping address

This update helps you collect addresses in formats that comply with local address requirements in these five countries, and gives your buyers a better checkout experience.

Learn more in our Help Center.

Collections now support multi-source and variants

Fri, 04 Sep 2026 20:37:05 +0000

This release expands collection capabilities to help merchants run complex merchandising strategies without workarounds such as duplicate lists or third-party apps. Previously, collections were created only by automated conditions or hand-picked products.

You can now build a collection from multiple sources, target specific variants, reuse other collections, and more. Highlights include:

Multiple sources in one collection. Combine automated conditions, hand-picked products, exclusions, other collections, and sources from apps in a single collection.
Variant-level collections. Build collections around specific variants, such as a size or color. Those variants appear on collection pages, in filters, and in supported sales channels, including Online Store and POS.
*Collections as building blocks. *Add a collection as a source inside another, so parent collections stay in sync when source collections change.
** Reuse across your business. **Apply the same collection in supported workflows such as discounts and taxes, including variant-level collections.
** Redesigned collections admin UI:** Use a visual grid for drag-to-reorder and bulk moves, list view for detail, and control over the sort order customers see on the collection page.
Sidekick support. Build and update collections with Sidekick on admin and mobile.

There are no breaking changes for existing collections.

Existing collections continue to work and are updated in the new admin experience automatically. You do not need to delete or recreate them.
If your store uses third-party or custom apps that interact with collections, ask your developers to update to API version 2026-07 to support these new capabilities. See developer instructions.

Read help docs for more information.

Shopify Managed Markets now available in Canada and the UK

Fri, 04 Sep 2026 20:37:05 +0000

Selling internationally is one of the biggest growth levers for Canadian and UK merchants and one of the most complex. Managed Markets removes that complexity by making Global-e your merchant of record for international orders. Your customers experience a localized checkout optimized for clarity and conversion, and you fulfill orders the same way you handle them at home. No surprise fees or delays

What you get

Transparent product pricing without surprise fees at checkout or delivery: International buyers see duties-inclusive prices, pay in their local currency, and have no surprise fees at delivery (DDP).
Built-in international tax compliance. Global-e registers, collects, and remits tax in the destination country on your behalf.
Discounted DHL Express and FedEx labels. Buy and print directly from your Shopify admin alongside your domestic orders.
Automatic tariff management. Managed Markets classifies your products and assigns Harmonized System codes for your products for smooth customs clearance & accurate duties calculations. Import tax and duty collection is guaranteed - you’ll never receive an adjustment.
Daily payouts in your local currency. CAD for Canadian stores, GBP for UK stores, processed daily by Shopify Payments alongside domestic sales.
Local payment methods with Shopify Payments

Learn more about Managed Markets – including eligibility, pricing, and set-up – in the Help Center.

Turn automatic hreflang tags on or off from your admin settings

Fri, 04 Sep 2026 20:37:05 +0000

Hreflang tags tell search engines which language or region version of a page to serve to which visitors. Shopify generates them automatically from your Markets language and domain settings.

The automatic hreflang tag setting is on by default, but you can turn it off if you prefer to manage hreflang tags yourself and want to avoid duplicate tags. To turn it off, go in your Shopify admin to Online Store > Preferences, and then change the setting in the Social sharing and SEO section.

New and updated staff permissions for payments, payouts, disputes, and tax documents

Fri, 04 Sep 2026 20:37:05 +0000

We've released four new staff permissions, giving you more granular control over who on your team can access information and manage settings. You can now grant staff only the access they need to do their job, without sharing full account capabilities. The new permissions are:
* Manage payments settings
* Manage disputes
* View payouts
* View tax documents

These are rolling out now and can be assigned to a staff member's role in Settings → Users → Roles → Permissions.

Learn more about staff roles and permissions in the Shopify Help Center.

View data access changes with the new app pixel activity log

Fri, 04 Sep 2026 20:37:05 +0000

We've just released the activity log for app pixels in the Customer events section of your Shopify admin. This helps merchants who share customer data with apps keep track of when and how that access has changed over time. The activity log lets you view the history of data access changes for each app pixel, right from its detail page. The activity log records every data access change from June 3, 2026 onward, so you'll have a complete history going forward. It's now available to all merchants using app pixels.

Learn more about the activity log in Shopify Help Centre

Roastidio.us Tagged with admin

How to Disable All Automatic Updates (WordPress Core, Plugins, and Themes)

Contents

Disable automatic updates via constants

Notes

Disable automatic updates via filter hooks

Notes

Codeless Way to Include External Directory in Sitemap | Digging Into WordPress

Add a directory without code

Step 1: Requirements

Step 2: Add a directory

Step 3: Add new Page

Check it out..

A few final notes

What about adding files?

Plan launches, events, and tests with clearer and more granular controls in Rollouts

The Plural Of Beef

AIforce: Salesforce’s New AI Interface Layer for Slack, Claude, and Lightning

Dreamforce 2026: One Message You Missed Is The Real Game Changer

Salesforce Timezone Offset: A Native Flow Alternative to Apex

SOQL Basics for Salesforce Admins

Salesforce Rebuilds Licensing Tiers and Adds Agentforce

Claudeforce Explained: Salesforce and Anthropic's New AI-CRM Partnership - Salesforce Break

What Salesforce in Claude Actually Does

The Underlying Infrastructure: Headless 360 and MCP

Governance in Salesforce Gets Reused

Should Salesforce Admins Care About Claudeforce?

Related

A new look for the Shopify admin

Multi-currency payouts now available in Australia and France

Palomar – a registry of Lean verified mathematics | What's new

Share this:

Bulk staff setup with CSV import

Recommended changes to checkout field settings are now available

Taxes now recalculate when you change an order's shipping address

Managed Markets is ending Delivered Duty Unpaid (DDU) support

Shopify Messaging now supports WhatsApp marketing

UPS return labels are now available

Localized address fields are rolling out to checkout and Shopify admin for Brazil, the Philippines, Kuwait, Peru and Panama

Collections now support multi-source and variants

Shopify Managed Markets now available in Canada and the UK

Turn automatic hreflang tags on or off from your admin settings

New and updated staff permissions for payments, payouts, disputes, and tax documents

View data access changes with the new app pixel activity log