I have deployed the Virto Commerce Manager to IIS successfully. However when I build the website and start Storefront I get an error when I click Let's Start.
What should the connectionString be in my Web.config?
I tried:
"http://localhost/admin/api/"
For the default installation should be http://localhost/admin/api/. Can you open the admin site? It looks like you trying to access /admin and it is not opening and it also looks like you running using IIS Express intead of just IIS.
How did you setup Virto Commerce (which guide or approach did you use)?
Your connection string is correct, but the Let's start link is not. It should point to the absolute URL http://localhost/admin while it points to relative /admin instead, so the full link is http://localhost:53032/admin and it is invalid.
You can navigate to http://localhost/admin manually and import the sample catalog. After that the storefront should show the home page with products.
Related
I just have deployed a VUEJS project to my Cpanel and have configured it with a subdomain as
https://web-dev.mydomain.xyz
it is working fine when I try to access through the exact domain name like
https://web-dev.mydomain.xyz
But when I try to directly access some routes like
https://web-dev.mydomain.xyz/posts?page_1
Then its returns page not found an error. So that I cannot share a specific page with anyone.
What I am doing wrong?
if the issue is at the VUEJS side or this is due to some misconfiguration of the project at the deployment server?
thanks in advance
This is a common issue. Your server needs to be configured to serve the application at that route.
Please read HTML5 History Mode documentation for more information.
When configuring Hybris smartedit to use compiled Spartacus in static web server (Azure Storage Account in my case), smartedit gets URL references to /cx-preview?cmsTicketId=.... This results in HTTP 404, as there is no such file available.
I have compiled Spartacus by running
ng build
Currently, my workaround is to have a dedicated virtual machine running
ng serve
And having all the needed dependencies installed. But this is suitable only for development usage.
I have followed instructions in https://sap.github.io/cloud-commerce-spartacus-storefront-docs/smartEdit-setup-instructions-for-spartacus/#page-title, apart for the last step, as Azure Storage Account can only hold static content.
Spartacus UI works fine from Azure Storage Account
It does look like your Site table hasn't been updated to reflect the location to your storefront: "/cx-preview" clearly shows a default URL from when smartedit and stortefront are in same origin within the SAP Hybris commerce platform.
So make sure to update the previewUrl field of the Site table for your given site.
Here:
https://sap.github.io/cloud-commerce-spartacus-storefront-docs/smartEdit-setup-instructions-for-spartacus/#configuring-smartedit-to-work-with-a-spartacus-storefront
you will find, amongst other things:
. Ensure that the WCMS Cockpit Preview URL is set correctly.
. In Backoffice, in WCMS > Website > your site, click the WCMS Properties tab.
. Set the WCMS Cockpit Preview URL to your Spartacus web site. For this example, it
. should point to https://localhost:4200
Hope this helps.
I have a .NETCORE application being an Aurelia Framework app. I also have a .NETCORE Web API. To publish these to the server I use the CMD .net publish --framework netcoreapp1.0.
I host this site on the Default Web Site which is pointing to the Aurelia app. Inside of this site I have another application being the web api. The site and API run great. I recently tried to create a Virtual Directory to server my images. Any time I try to navigate to //mywebserver/images I get nothing but 404 errors. I can play with the permissions and have it give me a 401.2 unauthorized, but any other time I just get a 404 error.
I can create a dummy website pointing to the IIS wwwroot folder, create a virtual directory and it works like it should, so I would think it has something to do with these published apps.
For anyone who stumbles across this question. Shortly after posting I came across some information on a site. http://www.jauernig-it.de/asp-net-coreiis-serving-content-from-a-file-share/
Matthias discusses that with .netcore Virtual Directories are basically dead and you should start using app.UseFileServer in your startup.cs file.
Thank you
I seems that the '404' Http return code is the default error code in published .netCore apps (I had this return with a sql server connection problem).
I think it is not related to Aurelia. use app.UseFileServer to handle your images.
We have a multistore magento setup thats still half in development. But we have 1 of the stores open with a test url.
e.g
test.domain.com
However when we go to: http://test.domain.com/index.php/api/index/?wsdl=1
I noticed that soap:address shows the main domain not the api url e.g:
<soap:address location="https://www.domain.com/index.php/api/index/index/?SID=vnl0ijdobf6ldj76pmc658rj92"/>
Which atm isn't live.
We have no issues with 3rd parties who come in on the V2 api but this doesn't seem to have a soap:address which I believe is the problem.
When I go to: http://test.domain.com/index.php/api/index/?wsdl=1 in a browser it shows xml.
When I try and make a soap call i get: looks like we got no XML document.
When I update my local hosts file with the new ip to point at the domain it will work.
But the 3rd party can't update their server because its shared hosting. Is there a way to change the API to point at the api url and not the base store url?
I had Magento SOAP API working perfectly until the client said Doh! We need it on this url instead, after I moved it it to that new url API will not run no matter what, I've made all the necessary url changes in the API script, Configuration, the DB and the site files.
Is there somewhere the old url may be encoded where I'm not finding it using a find and replace?
For instance, I created a full cPanel back up of the site, restored it to another server, whet back through and changed all the instances of the new url back to the old url in the db, site files and configuration and WHALA! SOAP starts working again..
Thanks!