We have to redo our joomla website, however we can't find our local customized template.
Is there any way to download the current used template? Or can I even use my ftp access to download the template folder, zip it and use that?
Thanks for your answers!
From the backend, you can't download it. But using FTP, you can download the folder, zip it and install it again if you want. That should work most of time for the simpler templates. If it's a bundle with a framework and other stuff, then it will fail because there are more files in other places.
The folder is within the /templates/ directory and depends on the name of the template.
Related
I have created an API in Django. It is supposed to take a request and pass the argument to allenNLP files to gather a computed response. I want to know how to run my django app in allenNLP environment and I want all the source code of allenNLP to be in a folder in my django project. Is it possible and how can I do it?
What you're looking for is running AllenNLP inside django.
You can add AllenNLP libraries in your requirements.py. Next, the .py file can be stored in any of your source code hierarchy.
In your views.py, where you are getting request and extracting parameters, you can call the .py file which contains allennlp source code.
Not sure about what AllenNLP files you're talking about, if it's code files, they can go in your regular source code folder, if it's a static files, like Image, CSV etc, they need to go in static folder.
Please clar my understanding of your requirement if the answer doesn't address your question.
I have a problem with dotCMS. I have a site which is uploaded to the Internet and I want to export it to take care of this site locally on my computer. I've downloaded all data/assets from Maintenance -> Export dotCMS Content. I have a zip file with all content from this site. I managed and configured dotCMS locally on my computer. I have no idea how I can get access in dotCMS to my site from that zip file. In Maintenance menu I have no option to upload this site. I've read about folder dotCMS/starter.zip but I don't have anything like that. Can anyone tell step by step, how can I manage my site from zip file locally? Thx
Create a new database for dotCMS and replace the starter.zip with your downloaded .zip. Start dotCMS and it should import your site on initial startup. There are some caveats - the databases and versions should match from the server you've downloaded the .zip from.
So to add a couple things to Will's answer in case a few more details help:
The easiest way to do what Will advised may be to start with a new dotCMS distribution.
Make sure the versions of both dotCMS and the database in the new installation match those of the site you made the backup from.
Go through all the normal install steps (including setting up a database), but before you actually start dotCMS, replace the starter.zip file in the ROOT (/dotserver/tomcat-8.0.18/webapps/ROOT) with your own ZIP file (renaming your file to starter.zip).
Alternately, if you want to start with an existing install.
You still need to make sure the dotCMS and database versions match those of the site you backed up.
You still need to replace the starter.zip file with your backup ZIP file.
In addition, make sure you create a new DB (and update the context.xml file to point to it) before you start up dotCMS. If you don't do this, the starter.zip file (your backup) will not get read when dotCMS starts up.
I have purchased a Joomla website template (including all content and images) from www.templatemonster.com/. When I was originally developing the website on my local machine using MAMP I created a folder under the HTDOCS parent directory and access the website by typing 'localhost\folder name'.
I have attempted to copy the files to the '/opt/bitnami/apps/folder name' assuming that this would be the correct method given that /opt/bitnami/apps/ contains the folders and files for the phpmyadmin dashboard, however this doesn't seem to work.
I followed the instructions as per https://docs.bitnami.com/installer/apps/joomla/#how-to-install-multiple-joomla-applications-in-the-same-instance, but this doesn't work because the conf directory doesn't exist within the template files. I assume this is because the Bitnami Stack includes the conf and htdocs directories under the Joomla parent by default, whereas in MAMPS the htpdocs directory would be the parent to the directories containing the content and so forth.
Is there something I am missing from this process?
Thank you for your help.
I would advise you the following:
First make a backup of /opt/bitnami/apps/joomla
Once the backup is done. Copy the template to /opt/bitnami/apps/joomla/htdocs
If it is a template with database contents you will also need to migrate the template database to mysql. The included phpmyadmin can be helpful.
You will probably have to modify the configuration files in case they are overwritten. Use the previously backed up folder for reference.
I am setting up a Magnolia-based website and trying to place a template script into the templates folder in the webapp. However, I cannot find that folder anywhere. All tutorials say that, if I go to this directory magnolia-5.0/apache-tomcat-7.0.40/webapps/magnoliaAuthor in my enviroment, I can get it, but I haven't managed it.
I attach an screenshot of my magnoliaAuthor folder in which every folder that is supposed to be there actually is, except for the only one that I need (templates).
Hope you can help me with this. Thanks!
What kind of template?
If it is jsp, you can just place it anywhere you want in that folder and reference it from the template definition.
If it is freemarker template, those are by default served from either the classpath or from repository, so for testing you can just upload it to the repo via templates app http://yourtomcat:port/magnoliaAuthor/.magnolia/admincentral#app:templatesApp:;
BTW if you install samples module (add magnolia-templating-samples.jar in your WEB-INF folder), it will create folder "templates" in your webapp and extract sample jsp templates in that folder.
HTH,
Jan
I'm using fossil to manage some home projects and keeping notes in the wiki. After running like this for a few months, I'd like to at least try to use embedded documentation; mainly so as to be able easily to go back to previous versions.
I've studied the website page about managing project documentation which confirms that this is a technique I want to follow up, but I can't make out how to do it.
I've cut-and-pasted one of my wiki pages and added it to my fossil repo, but I can't work out where it should go in the directory structure to be accessible as described on the above page.
I've tried in a few places none of which worked. The document is currently %fossil-root%\doc\foo.wiki, (I'm on Windows), where %fossil-root% is the directory holding _ _FOSSIL__ (slighly mangled filename because of markdown), but having started a server with fossil ui, when I point my browser at http://localhost:8080/doc/foo.wiki, fossil presents me with a nicely formatted page saying it can't find index.html. I created /doc/index.html to see what would happen, but it made no difference.
Please can someone help me out, and/or point me to an example repository containing embedded documentation or another "how-to" document.
If your document is located in %fossil-root%\doc\foo.wiki, you can access it at the following URL:
http://localhost:8080/doc/trunk/doc/foo.wiki
This URL breaks down as follows:
http://localhost:8080 is the root URL to access Fossil when you run fossil ui
/doc signals that you want to access embedded documentation
/trunk indicates the checkin containing the documentation you wish to access
/doc/foo.wiki is the path of the document inside the repository
Instead of trunk, you can also specify a tag, or a branch name, or even a hexadecimal checkin identifier.
In the URL you were using, http://localhost:8080/doc/foo.wiki, foo.wiki is interpreted as the checkin name, and no document path is specified, which logically means Fossil won't find anything.
As for an example repository containing embedded documentation, the homepage of the Fossil website itself is a prime example:
https://www.fossil-scm.org/index.html/doc/trunk/www/index.wiki
where
https://www.fossil-scm.org/index.html is Fossil's root URL
/doc indicates a request for embedded documentation
/trunk indicates we want to fetch files from the trunk
/www/ is the path to the requested file inside the repository
index.wiki is the name of the file inside the repository.
So, in the 'trunk' branch of the repository, the file www/index.wiki contains the home page of the Fossil website.
You simply need to put the documentation under the %fossil-root%\www\ directory (or any other directory under version control) in your repository and then you can, for example, add the following line to your header's mainmenu section to link to it:
html "<a href='$home/doc/trunk/www/foo.wiki'>Documentation</a>\n"
As I said, it can be any directory under version control. To test this, pick any file in the repository, let's say a README file at the top level, and go to http://localhost:8080/doc/trunk/README. You should see the README file load up in your browser in a raw text format. By putting wiki or html files under a particular directory such as www you make it easy to organize the files that you specifically want rendered as documentation, which makes it easier to link to them.
http://www.fossil-scm.org/index.html/doc/trunk/www/embeddeddoc.wiki
After fossil 1.33, just prepare your document in the repository.
If the wiki file is put in
/doc/index.wiki
And use web browser to setup -> Admin -> Configuration.
There is a "Index Page" field, fill in your main index.html.
For example:
/doc/trunk/doc/index.wiki
Or if you just want the released version:
/doc/<version>/doc/index.wiki