storefront | high performant headless eCommerce Storefront | GraphQL library

You can take a look at the Spartacus Session Management documentation.

• If you need to send the user token, by default it is included in the header of every request made to "occ". This means that if you want to have this same behavior for an endpoint not in OCC you will need to extend and overwrite AuthHttpHeaderService more specifically the isOccUrl method so that it returns "true" for occ endpoints and your external endpoints. It will look like this:

B2B sample data comes packaged with the latest spartacus releases in the 2005 sample data addons attached to releases.

https://github.com/SAP/spartacus/releases

If all the products in the result have the same value or no value at all, the facet won't show. The facet will only appear if it will make a difference in the result when the user filters by it. Can you check if that's the case?

I don't think the functions.php file has anything to do with it - usually HTML structures like this are created in template php files which are in the themes folder - either on the top level of that folder or as "template parts" in an according subfolder. You have to edit those( or actually those among them that are used by the pages you are referring to), changing all

However, since any not-selfmade theme will be updated every now and then, those changes would be overwritten with updated files when available, it would be necessary to create a child theme, which only contains those templates which you want to change (see also https://developer.wordpress.org/themes/advanced-topics/child-themes/). Then again, updated themes might contain template updates which are necessary, so you'd always have to check which details were updated in that particular template file, integrating it into your child theme templates or editing the updated original themes and using them in your child theme.

P.S.: I think the title of your question is a bit misleading: In the question text you are asking about certain title tags in the product pages, not about parts of the menu, aren't you?

In app.module.ts use this baseUrl link baseUrl: 'https://spartacus-training.eastus.cloudapp.azure.com:8443',

As I could not find the source of the problem, I started from scratch by changing my hosting solution. Once the files were uploaded on the new server and the configuration files were adapted, the shopping cart works normally again.

You can use the woocommerce_cart_actions hook.

This code:

What do I have to select to get the same b2c features as for the 3.1 schematics

To have the b2c configuration, you need to select the "b2c" configuration on the first prompt. Here, "b2c" means only some b2c-related configuration, and it's not related to b2c features. The second prompt will ask you which additional Spartacus features you would like to install. Here, you can just press "Enter" if you don't want any of the additional features. The exception to this is our new "User" library which is mandatory to be installed.

Why are basic things like "Cart" and "Product" even presented as option? or are they preselected already because I chose "b2c"?

The reason for this is because some clients like to use Spartacus as just a catalog site, without any cart functionality (for example). Currently, these libraries only contain some extra features related to cart and product and the core mechanisms for these features are still present in core and storefrontlib. This is part of our effort to improve the code splitting and lazy loading. And again, the second prompt doesn't change based on your choice between b2c/b2c configuration.

What is the purpose of useMetaTags?

Meta tags are explained in our docs:

I do think the issue is theme-related as your code does work when I try it on a test site, though I don't have Storefront set as the theme.

You could try a string replace: