i had created new wcms custom site along with content and product catalogs by creating similar extension as electronicstore, my extension name is dastore. for this site i want to create new spartacus site similar to electronics-spa.
in spartacussampledataaddon, i had followed impex files of electronics store and created all the necessary folders and files. Modified SpaSampleAddOnSampleDataImportService.java to consider my custom site also for import.
after build and startup, ran an update by selecting "dastore" and "spartacussampledataaddon".
But still my impex files were not considered for execution.
Please help.
We need to run update including dastore, spartacussampledataaddon, addonsupport(if you have impex on any of your addon, you need to include this, then your addon impex will be part of sample data and core data events)
Related
we are working on SEO for one of the content related (article, videos) website and using wordpress template to build the website. Now if I use yoast generated schema the standard webpage schema is being used to all the pages which I really don't want and won’t be useful. I need to insert the schema according to the page category that can be manually coded (json-ld) or using any plugin that supports category wise schema uploading.
Please help me how to add schema code manually to wordpress website each page or any plugin that will help me to do the same.
you can use to Custom Fields.
you need add your schema code to article and Video Custom field and choose that on every post.
Need a little help. Can anyone guide me on how to add schema mark-up code to magento 1 website? I tried to search it on YouTube but didn't find anything helping
Schema type : Product
Website niche: E-commerce
Please help. Thanks in advance!
I'm sure I don't have to tell you that Magento 1 is now officially deprecated since over a year now, but I do just in case!
To add tags from schema.org, you need to add the proper tags in the .phtml files copied into yout theme directory as you shouldn't edit core files. The templates usually copied are these ones:
app/design/frontend/[package]/[theme]/template/catalog/product/view.phtml
app/design/frontend/[package]/[theme]/template/catalog/product/view/media.phtml
app/design/frontend/[package]/[theme]/template/catalog/product/view/type/default.phtml
app/design/frontend/[package]/[theme]/template/catalog/product/price.phtml
But maybe some other templates are to be edited in your theme, depending on how the theme is set up.
Then, edit each .phtml files to add the necessary tags that you need. Save the files and empty Magento cache, as well as your browser cache.
You can test the work done using Google's structured data testing tool (https://search.google.com/structured-data/testing-tool/u/0/).
This guy here has a good tutorial on how to do it: https://www.groovecommerce.com/ecommerce-blog/developers-toolbox-adding-rich-snippets-to-magento-products-with-schema-org-tags/
I'm trying to build a sample app in Wit.AI, with a lot of entity values and expressions. Thus, to create that app manually is not an option.
I've tried their "import" feature, but it seems it doesn't work very well or it might be very capricious about the zip. The things I've done and nothing gave a result:
Download a zip from another app in my account
Change the zip command in order to work for the new app
The changed files are expressions.json and a single file in the entities folder, describing an user-defined entity.
Zip the whole folder in order to preserve the structure of the ZIP
Nevertheless how many approaches I've tried (format the JSON and etc.) nothing worked! The server returns 400 Bad Request response.
Further, I've tried with their Web API, but to no avail again. When I'm updating the values of an entity the server responses with Success, the response doesn't contain the new values...
I've checked this article Error importing app from backup on wit.ai and many others as well as some issues on GitHub, but again...nothing helped ;)
So, if anyone could help on that...He/she gets a beer! :)
When you create a new app, you can simply upload the the zip file in Import your app from a backup, and create the new app.
To be sure to not include any redundant files in the app zip file, it is important to use the following to zip app files:
zip AppName.zip AppName/app.json AppName/entities/*.json AppName/expressions.json
and upload AppName.zip.
Note that, the name of new app, zip file, and app name in app.json file, all should be the same (here AppName).
I'm looking to create a central repository for all of our published API documentation using DocFx. I have documentation auto-generated via my build (using TFS) and published through my release (using Octopus) just fine for multiple individual sites. However, I'm wanting to pull it altogether in one location. The thinking is that through a parent site you could filter content in any of the individual sites without having to drill down into them. Do you have a recommendation on how to do this?
Also, within this same documentation repository I want to provide the capability to search by all of the meta data (project-level documentation) across the hundreds of projects in our portfolio. This will give our BA, DEV and QA teams easier access to what all our systems do. I like the "filtering" capability built into DocFx, but I'm wanting full-text search across all of the meta data. Do you have a recommendation for this functionality as well?
To change the location of the docfx output, edit the docfx.json file and specify the dest value. By default it is "dest": "_site". For more formatting guidance, reference: https://dotnet.github.io/docfx/tutorial/docfx.exe_user_manual.html.
Regarding full-text search, that is possible by simply ensuring the ExtractSearchIndex post-processor is invoked (in order to generate an index.json file of keywords) and that the global _enableSearch value is set to true in the docfx.json file. A snippet from that file would look like:
"postProcessors": [ "ExtractSearchIndex" ],
"globalMetadata": {
"_enableSearch": "true"
}
For your first question:
I think what you expect is like the .NET API Browser. The source code behind this page is not open to public, so you need create this page by yourself, through collecting xrefmap.yml from multiple sites, and extract the needed data into this page.
For your second question:
DocFX uses Luna to scan all the output files and generate an index file called index.json for later search use. In your case, you should want to limit the search scope only in the metadata you defined. This is also not supported by DocFX by default. You can also use Luna in your central place to search these meta. You can create your specific index.json for each project first, and the cental place to collect them for the search page.
I am helping a client redesign their website through Hubspot. Their existing site is within Hubspot and their new website will also be within Hubspot. I am attempting to run the development through Hubspot's Content Staging as per this link: https://knowledge.hubspot.com/website-user-guide/how-to-redesign-and-relaunch-your-site-with-content-staging
The problem is that this appears to be on a per page basis rather than a per site basis. A problem with this is that I am unable to stage files such as the primary CSS file, or other CSS/JS files that I need to make changes to, but that the existing website will need to keep untouched throughout development.
Does anyone have any experience redesigning a Hubspot website who may have some advise for me? What am I missing?
Thanks!
When I'm redeveloping a HubSpot site within a client's portal, i'll do it on a template by template basis.
So for example, if you're making a new home page, just attach any stylesheets and scripts you need in the template file itself - found in the Edit > Edit Head menu. Here you can disable the Primary CSS file, and you can also disable domain specific stylesheets (the ones you add in Content > Content Settings) so that your template is only using the assets you want it to use.
Using this technique, you can work on individual templates, and then stage any pages that are using said templates independently of the rest of the website. Finally when you're ready to make your changes site wide, merely move your assets from the Edit head area within your template to the Content Settings area.