-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Bug: Releases missing submodules, leads to old bugs like: Appended double slashes to ROOT_URL #962
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@NoodleBB What Wekan version are you using? This is already fixed #932 |
Can you look at this? |
I've setup another Wekan demo that points out the problem. There you can test it for yourself. The ROOT_URL is Demo-User: yeswekan Steps to reproduce:
@xet7 |
@NoodleBB I took a look at the demo site you provided. It appears as the javascript is an older version. Make sure you properly rebuild wekan using the code below. source app.env
# Rebuild meteor stuff
rm -rf .build
meteor build .build --directory
# Install depends
cd .build/bundle/programs/server
npm install @xet7 Please close this issue |
@xet7 @Serubin |
@NoodleBB Releases get old quickly. I do tests and merges on devel head. |
@xet7 |
@NoodleBB Hmm, maybe I'll check it sometime. |
Moved to #969 |
@NoodleBB Downloading the tar likely does not download the required submodule and will default to using the default flow-router. Try pulling recursively using git and rebuilding. |
@Serubin The unit-tests should throw an error. |
@NoodleBB We don't have any unit tests. |
@NoodleBB I moved your issue back to here. We could have some checks and error messages for this. |
@NoodleBB Doh, it seems to be my problem. I did not update submodules for releases. I will update releases later. |
Okay. This explain some things.
No problem. Organise it the way, that you'll have the best overview. 🙂 8000 p>
Good idea. 👍 |
@NoodleBB There could be some tests somewhere, but I have not tried to find them yet. Usually I just build Wekan and test does it work or does it crash. I keep Wekan devel head working. Travis and Docker builds have some tests, but they are broken. I can build Wekan and it works great though. |
I know, writing unit-tests is boring. |
@NoodleBB I updated release v0.18 to include submodules. Can you test does that .tar.gz work for you now? |
Sure. |
Yes it works. 👍 |
Great! :) |
@NoodleBB I reopened #973 , it can be continued there. |
Perfect. |
So the doubleslash bug was reactivated 😞 |
This appears to be back. It works in v0.24, but not in v0.25-v0.29. |
Can you reproduce this bug? |
FWIW I was testing the docker builds from wekanteam/wekan. |
It's just a docker problem It starts from here. f0f27d1#diff-3254677a7917c6c01f55212f86c57fbf |
Is it possible to fix that without adding git submodules back? For example, should I fork whole meteor repo to Wekan and add changes to there directly? |
If I'm catching the drift, the cache isn't being invalidated. Is that correct? |
Try with the same path as the source installation (https://github.com/wekan/wekan/wiki/Install-and-Update#install-and-build-wekan)
|
I tested with those changes and could not reproduce bug anymore. Is it fixed for you too, using wekanteam latest docker image? |
OK. |
Fixed at 4fdcc14 |
This still happends when using snap, when I tried to add wekan to sub-url like example.com/wekan , and there was Drupal website at example.com . I'll try to apply previous fixes to this. |
Please test newest Ubuntu Snap, is double slash bug now fixed. It seems to work for me. |
With Nginx and Wekan at sub-url it works for me, there is no double slash bug, with Nginx and snap settings at this page: |
I'm running Wekan v0.71 (with Meteor v1.6.0.1) on Windows Server 2012 R2 (installed it from source). If the environment variable |
Problem: Bind Wekan to a path leads to double slashes in the URL, only when clicking on a card and when you to "export board".
Steps to reproduce:
ROOT_URL=https://mydomain.org/wekan
node ~/wekan/bundle/main.js
https://mydomain.org/wekan
Finally: Inspect the URL and you'll find double slashes.

When you remove one of these slashes, you'll see the open dialog.
Rem.: This bug could be related to #907.
The text was updated successfully, but these errors were encountered: