When I am trying to access my django site, it appeared the ImproperlyConfigured error say that "Module "django.template.loaders.filesystem" does not define a "Loader" callable template source loader".
I use Bitnami Django Stack and this is not the first time I installed it, so I think that there is the conflict between the old and new one somehow. I tried to clean the previous installation many times but it still be the same.
Sounds like you're trying to run the site on an older Django version.
In the settings.py file try 'django.template.loaders.filesystem.load_template_source' instead of 'django.template.loaders.filesystem.Loader'. The Loader name was changed in more recent versions.
Related
I am trying to work out how to deploy an aurelia app, it runs in development with au run. but I need to deploy it into a path which is not the root of the web-site. ie at '/site' not '/'
when I deploy I get an exception from the router: ERROR [app-router] Error: Route not found: /site/
I think it may be that I need to specify a baseURL in one or more places?
but can't see how I can:
make it work in the development environment at /
make it work in the deployed environment at /[any-site-path]
avoid building in knowledge of '/[any-site-path]' to my development environment or bundles, as the path wont be known until someone comes to deploy the code?
i found this question but that seems to apply to an out of date version of the code.
I am using Aurelia 1.0 and building using the au-cli
Any pointers would be useful.
Looks like this is a bug that has been fixed in a more recent version.
I have just gone through and applied the latest versions of:
"aurelia-bootstrapper": "^1.0.0" -> "^2.1.1"
"aurelia-cli": "^0.24.0" -> "^0.26.1"
"aurelia-tools": "^0.2.2" -> "^1.0.0"
And i can now deploy my application to a site sub folder without specifying any url content in the code or html files!
So I can satisfy all 3 of the criteria in my question.
Note the aurelia-cli update (0.25.0) requires a change to the main.(ts/js) as mentioned in the release notes.
Hi i am trying to create a yii application and i am got this issue tried google but not able to find the solution how can i resolve this,..?
This is my error:
Error: Unsupported VCS specified. Currently only git and hg supported.
And what actually this error is..?
yiic webapp d:\xampp\htdocs should work.
Notice the backslashes.
Or, perhaps better, since the app generator supports relative paths, navigate to d:\xampp and simply run yiic webapp htdocs.
That said: why are you using Yii 1 ?
It is really old, and does not receive any updates.
Yii 2 is so much better :)
I have created an authentication module which was build against
ejabberd 16.02 and runs fine when auth_method is set. It also works against
16.03.
However, from 16.04 onwards it gives me the error "[error] ignoring
option 'auth_method' with invalid value: [jwt]"
I checked the code diff between those releases and the only change
seems to be to the mod_pubsub.erl file, specifically adding the
following:
ServerHost = serverhost(Host),
+ ejabberd_hooks:run(pubsub_subscribe_node, ServerHost,
+ [ServerHost, Host, Node, Subscriber, SubId]),
https://github.com/processone/ejabberd/commit/639c2fb6401391663206c0e4c946d1a699689ac7
I have tried disabling this module and even deleting the beam file as
i don't use it, but i can't seem ti get round it.
Does anyone have any insight as to why these changes will have broken
my authentication module?
My source is at the link below, but as i say has worked fine for a year:
https://github.com/ParamountVentures/ejabberd-auth-jwt
The answer is that from 16.04 onwards you need to drop the .erl file into the ejabberd src folder and compile it with the source. Dropping in the .beam file to use alternative authentication modules no longer works.
I did an upgrade from Typo3 4.5 LTE to 6.2 LTE, following the instructions found here: stack overflow
Now during the process of using the Upgrade wizard the Excepiton #1314516809 occured.
Then I went to the db using my php-myadmin and corrected the CaseSensitive-Value as recommended here:wiki.typo3
but the error stays. Rereading the code i realized, that the files, which could not be found, had doubled file extensions like
File /_migrated/RTE/RTEimage.jpeg.jpeg does not exist.
How can I get rid of them?
Maybe this will help.
Migration of RTE images
You must modify the database table sys_file_storage and remove the image entries which cause problems. The images of the migration folder should not remain here.
I've performed an update from typo3 4.7.20 to 6.2.15. The process worked fine and there were no critical errors while running the install tool.
The frontend looks fine but the backend is broken:
I've removed all uncompatible extensions before I run the update. I've also checked all settings in the installationtool und deleted the temp/cache folder first.
I've got the feeling that the error is caused by the TemplaVoila! extension, I'm using v. 1.9.8. Firebug does not shows any error.
Does anyone had a similar problem and have already solved it?
Thank you very much!
I have come across this one multiple times. More often it is because there is a broken TBE_STYLES. I suggest you look around for $TBE_STYLES in your typo3conf folder and disable it for the time being. Most likely it will be in the extTables.php or some other file which is included dynamically.
seems BE is working, but you css does not got loaded.
check your 'web inspecter' to see if you get errors on loading CSS.
clear your cache (remove everything in typo3temp) and try again