- <span class="label">@T("Products.Availability"): </span><span class="value">@Model.StockAvailability</span>
+ <span class="label">@T("Products.Availability"): </span><span class="value" id="stock-availability-value-@Model.Id">@Model.StockAvailability</span>
I think in your case will be easier just to include the store id to the locale resource name, so that you can have different locales for each store. The disadvantage for this will be that there will be no default setting and you will have to add these locale resources for every store. But I think that this was what you needed.
Soin order to achieve this just open the Themes/Motion/Views/Common/Footer.cshtml file and edit it as shown below:
<li class="phone">@T("SevenSpikes.Themes.Motion.Common.Phone" + storeId)</li>
<li class="mobile">@T("SevenSpikes.Themes.Motion.Common.Mobile" + storeId)</li>
<li class="email">@T("SevenSpikes.Themes.Motion.Common.EmailName" + storeId)@T("SevenSpikes.Themes.Motion.Common.EmailAt" + storeId)@T("SevenSpikes.Themes.Motion.Common.EmailDomain" + storeId)</li>
<li class="skype">@T("SevenSpikes.Themes.Motion.Common.Skype" + storeId)</li>
This issue had been fixed and uploaded on our site. If you are running an older 3.80 version of the plugin, you will need to download it again from your My Downloads section and replace the plugin folder in your nopCommerce website with the newly downloaded.
Please let me know if the issue still exists after the update.
You are right that locale resources cannot be used in a multi store scenario while settings cannot be used in a multi language scenario. So that is why we have decided to use locale resources. Unfortunately, nopCommerce misses locale resources per store. So if you can let me know what is the case with your setup I can either let you know how to transform the locale resources into settings or can think of another solution depending on your configuration.
Hope that helps.
Unfortunately, there is no way to use some kind of tokens in the topic pages as they are plain HTML. But you can use the "/" symbol for a store URL. So instead of http://www.yourstore.com/standard-plan you can just write /standard-plan and it should work. But what is more interesting is that you need to change the links after an upgrade - how the links are changed after an upgrade. They seem to have nothing in common.
Hope that helps.