I just installed Sylius and noticed that there are 2 backend sites. The installation documentation directed me to /admin. The site frontend has a link to /administrator.
What is the difference?
/admin is the original backend. /administrator is the new backend. See this article: http://sylius.org/blog/backend-redesign
There are also some differences in how products are created. When I created products in the old backend, it generated an error when displaying the product list in the new backend. I went back to the old backend, deleted the products and everything was fine again.
Nope, /admin is the new one,
Have a look at the last security config file here: https://github.com/Sylius/Sylius/blob/master/app/config/security.yml
/administration is part of the SyliusWebBundle which is no more used (https://github.com/Sylius/Sylius/pull/5535)
Related
I have 2 projects Symfony plus react.
They exist in 2 directories and react app uses Symfony app as api backend.
I tried to figure out the best way to connect it and I used Apache Alias
(/front -> my frontend directory because adding /api - backend dorectory broke backend )
Now..
Frontend app uses things like: .
I could add /front to url but i guess this isnlt right and my app shouldn't care what the aliases are.
What would be the best way to fix that?
Is there a way to configure it in apache or should I add some global variable before every url or is just putting front project inside backend project?
So basicly I bought a domain and created subdomain for backend and everything works well.
Following a migration, I am trying to reconfigure TYPO3.
The backend is accessible by its url and I manage to connect. But the home page for example gives me the following error: The page did not exist or was inaccessible. Reason: No site configuration found.
All pages are not accessible by their url normally but are accessible through different query parameters, like /index.php?id=2&L=0.
I already tried to replace the .htaccess with the basic one provided by TYPO3, I also checked the Apache configuration and everything seems to be ok. I am not familiar with the TYPO3 CMS so I don't know if some of these configurations are done directly in its files. To me, it seems to be a mod_rewrite problem but I can't find it.
Someone would have a solution or at least a track to solve this problem?
As stated in the error message that you've posted it seems that the site configuration is missing. In the TYPO3 backend you can create new site configuration via Site Management => Sites.
Please check the site handling documentation for details.
The Spartacus seems to not update the base site in some scenarios when it is loaded with SSR. This happens mostly when we had just deployed the app or, in some cases, when you navigate from one site to another.
To reproduce this issue, you have to configure at least two sites on SAP Commerce and it's recommended to edit the "hosts" file in the local machine, to access the production-like URL. For example:
127.0.0.1 yourFirstDomain.local
127.0.0.1 yourSecondDomain.local
Then, run the Spartacus with SSR, access one of the sites, and edit the URL to access the second one.
To test to see if the base site was updated, I subscribed to the Spartacus base site service and logged the base site Id. When I access the first site, it logs the correct Id. But when I access the second site, editing the URL, the log does not occur and, although the URL changes correctly, the site (data, look, and feel) doesn't change and remains as the first one.
Is this a bug or something that could be configured?
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!
Does anyone know if you still need the sf404.aspx mapping for Sitefinity 4.4?
I'm trying to run a new test SF 4.4 project, but when I try and login the page just gives me the following:
HTTP 404 cannot find /sf404.aspx (this was mapped like that for Sitefinity 3.7)
I then changed the IIS 404 configuration from sf404 to default and now I just get HTTP/1.1 404 Object Not Found.
The project works through Cassini, but not through IIS 6.
Any ideas?
Regards,
Jacques
the sf404.aspx page is definitely only used for Sitefinity 3.x and should not be mapped in a Sitefinty 4 website.
If you are attempting to run a newer version of Sitefinity on IIS6, you need to make sure to use a wildcard mapping so that all requests go through the ASP.NET engine.
This page details everything you need to setup to run Sitefinity on IIS6: http://www.sitefinity.com/documentation/documentationarticles/installation-and-administration-guide/install-sitefinity/configuring-the-iis-to-host-sitefinity-projects
You might also find this blog post helpful: http://www.sitefinity.com/blogs/joshmorales/posts/11-02-23/installing_sitefinity_4_on_iis_6.aspx