content staging – How to delete/unschedule scheduled updates for product programatically in Magento 2 commerce edition?

The interface you mentioned is correct, but there is much more useful information inside the model MagentoCatalogStagingModelProductStaging.

In that model, we see the function unschedule() defined as:

/**
 * @param MagentoCatalogApiDataProductInterface $product
 * @param string $version
 * @return bool
 */
public function unschedule(MagentoCatalogApiDataProductInterface $product, $version)
{
    return (bool)$this->entityManager->delete(
        $product,
        (
            'store_id' => $this->storeManager->getStore()->getId(),
            'created_in' => $version
        )
    );
}

After looking at my own instance, I see that all the created_at values in the database are set to 1, I don’t personally use the schedule update feature but it would seem that you would add 1 to the version when running schedule().

I would recommend you open the model/controller for the scheduled updates page and see if you can get any more information about how the versioning system works from there next.

Edit:
Another file that seems to get closer to the answer you are looking for is MagentoStagingModelEntityUpdateActionDeleteRemoveAction.

In it, it passes $this->versionManager->getVersion()->getId() as the version where versionManager is a MagentoStagingModelVersionManager.

themes – What is the correct way to set up a staging server and use github for version control?

I have WordPress site at /var/www/contoso/html (contoso.com) running on a CentOS 8 server. I would like to run a new theme and make some frontend changes to it to make it match the look and feel of the old theme. I imagine that using a staging instance is the way to go.

Is the proper approach to copy site files to /var/www/contoso-staging/html (dev.contoso.com) and use a copy of the database? Or would it be possible to simply create a read-only database user and use the production database?

Also, I’d like to use version control for this. Would I create a GitHub repo for the production site and another for the staging site? Once the changes are finalized in staging, what would be the proper way to copy them over to live site?

If you have any suggestions outside of this, or if I am not on the right track, please feel free to offer your thoughts.

Thank you.

architecture – how to configure the staging environment vs production environment

I apologize for the question, however I am newbie, for software development process we used to set up 3 environments : integration , QA , master .

recently my boss asked to add a new environment staging that will mirror the production environment for further testing , so in the production environment we are configuring and using kubernetes, SSL, Load balancing , and others do I need to use them in the staging environment as well ?

also what are the differences to keep in mind between setting up a staging vs production environments

SharePoint SPFx webapp on staging site

I created a SharePoint SPFx react webpart that is now deployed on one of my SharePoint sites.

I want to continue to make updates to this webpart. I “cloned” my SharePoint site so that it can be my staging site. I’m currently using workbench to view my webpart on a local level. I want to now deploy my app onto my staging SharePoint site so that my clients can view the updated webpart and once approved I will then move to production SharePoint site.

However, when I add/deploy my app into the SharePoint App Catalog, it updates for both my production and staging SharePoint site since they both are using the same app.

How should I approach this? Should I rename the webapp every time I want to deploy to staging? For example if my app is called “contract-form” should I name the app “contract-form-test” when deploying/packaging the bundle?

Also a side question: In my app I reference links for example https://mysite.sharepoint.com/sites/Contracts/SitePages/PageName but on my staging site it’s ContractsTest instead of Contracts should I continue to just replace all links in the app every single time or should I make these as two separate apps? And when the client approves I do all changes again on the other one?

importing exporting – How do I export content from staging to production?

I’m looking for a way to export individual content items from a staging website to a production website. I’ve found the node export and content synchronization modules as possible solutions but I’m not feeling comfortable about using those modules on Drupal 9.

Anyone have any experience with this on Drupal 9? Any other modules I should be looking at?

importing exporting – How to export content from staging to production website in Drupal 9

I’m looking for a way to export individual content items from a staging website to a production website. I’ve found the node export and content synchronization modules as possible solutions but I’m not feeling comfortable about using those modules on drupal 9.

Anyone have any experience with this on drupal 9? Any other modules I should be looking at?

configuration – How can I merge a content type’s fields and settings from dev to staging?

I have an existing content type on staging. On dev we’ve added a ton of new fields and display and form setting changes, etc.

It’s not practical to go through the config files and find all of the many dozens if not hundreds of interconnected config files related to the content types, its fields and its settings.

So I heard Features is the way to go (even though I thought config sync in D8 was supposed to make Features not needed anymore).

So I’ve created my Feature. Keeping it simple I just checked the single content type. Saved my feature module and moved it to staging.

When I try to enable to the module I get a screen full of “unable to install” because the configuration already exists errors. Ugg.

So I read that I should remove the configurations. But this removes content and/or associated configurations like vocabularies.

Surely there must be a practical way to merge a content type from dev to staging?

sql server – Using a staging table in WHERE clause slows query a lot

I seem to have hit a wall with this issue. I have a fairly basic query which has several tables in the join and in the WHERE clause, the person running the query enters in some values. The query takes about 3 to 6 minutes to run.
I am automating this process using SSIS and I staged the values being entered so I can pull it in the WHERE clause.

My WHERE clause looks like below –

WHERE EXISTS (SELECT 1
FROM BI.Staging_Table A
WHERE A.case_number = B.case_number)

B.case_number is a table that I am joining to in my FROM statement.

Appreciate any input or even an alternate way of doing this. Thanks

P.S – The tables in the join are all on a linked server, the staged table is in a different database

plugin development – ReCapcha set up on staging site

I’m setting up a reCapcha for a client’s site and I’m not sure if I should use my Google account to generate the key, or the client’s, or if it even matters. Also, the site is a staging site until it goes live so the url will be slightly different when it is live. Will recapcha even work with the staging url, or will I have to get a new code when it goes live and the /staging drops off the url?