By james1212 on
I installed DrupalCMS 2.0.0 on my server with PHP 8.3 and Mysql 8.0. The installation went successful. However on editing the site and clicking on the "full content template" on the top left corner, the script throws 404 Not found error.
Upon further debugging I found that the script is redirecting to the url https://domain.com/canvas/template/node/page/full/ where as I have installed it in a sub directory so ideally it should redirect to https:/domain.com/drupalcms200/canvas/template/node/page/full/
Is this a bug in the installer to keep the support for sub directory installations ?
Comments
It could be a Drupal CMS bug
It could be a Drupal CMS bug ... or a server set up challenge? See for example https://www.drupal.org/forum/support/installing-drupal/2022-02-17/run-dr.... If not, please create a Drupal CMS issue.
My guess is that this is
My guess is that this is actually a bug in Canvas.
Can you give me a little more information about how this happened, so I can relay it to the Canvas devs? A screenshot of exactly where you were when you clicked the link that redirected you incorrectly, would be very helpful. It is also possible that this is fixed in Canvas 1.1.0 (released today), though I have no idea for sure. If that is the case, you should be able to update to the latest version of Canvas by running `composer update drupal/canvas -W` because Drupal CMS does not (and will not) pin dependencies.
I am not able to attach the
I am not able to attach the screenshot here. Hence mentioning the steps.
I also tried updating the canvas to the latest one (1.1.0) and still getting the same issue.
Steps to reproduce the error:
1. Login into the admin panel.
2. Click on the drupal icon on top left corner.
3. Click on edit at top right corner.
4. Access the "Template" section and click on "Full content template"
Reported as a Canvas bug:
Reported as a Canvas bug: https://www.drupal.org/project/canvas/issues/3572432
Is there any ETA for the new
Is there any ETA for the new version with fix, if the issue is resolved, ? or can I get the patch file of that fix?
Just wanted to follow up on this.
I tried the DrupalCMS 2.0.1
I tried the DrupalCMS 2.0.1 version expecting that the issue will be resolved however I am still getting the same issue.
Is there any patch file which will is helpful in resolving the issue.
We have hold on our DrupalCMS package for this issue and want to release the same if the issue gets resolved.
According to the latest in
According to the latest in https://www.drupal.org/project/canvas/issues/3572432, this is probably fixed in the HEAD of Canvas (most likely by a different issue) so there is nothing to do but wait on the next release. I don’t know when that is; Canvas releases on an ad-hoc basis.
Because Drupal CMS does not pin dependencies, I strongly recommend against patching anything. It is highly likely to break new installations, seemingly at random.
Why is it necessary to hold the release of CMS 2.0.1? When Canvas fixes this, CMS will not release a new version (because, as I said, we don’t pin or lock our dependencies in any way). Drupal CMS has many other dependencies and many of them have bugs too, but AFAIK you are not holding releases over those bugs. Can you clarify why this issue in particular is so problematic?
We were waiting for the
We were waiting for the confirmation.
Now we have launched the latest version and are waiting for next CANVAS release to fix this issue.
This usually happens when the
This usually happens when the template or page isn’t published, moved, or the URL is incorrect. A few quick checks:
Often, one of these steps fixes the 404 issue immediately.