I ordered a vserver with Plesk, installed Moodle through Plesk and worked some months on it.
The domain for Moodle is www.urltomyserver.com/moodle. I would like to change it to just www.urltomyserver.com. Thus I would like to change my document root in my hosting settings to httpdocs/moodle for this domain. However this does not work:
Unable to change document root: It is impossible to change document
root because there are web applications installed on this website
I know that when I change the document root, I need to make changes to the Moodle config.php file. So I understand the warning and I still would like to change the document root. Is this possible? Maybe directly through the shell?
Otherwise the only option that I see and that I would like to prevent is to make an backup from Moodle, de-install the application through Plesk, install Moodle manually and then change the document root.
Is there a way around that?
According to an answer on Plesk Support:
In order to change the document root, the problematic application should be uninstalled.
It's also mentioned here as well.
It should be possible to directly change your vhost.confor document root via shell. I think this would the be easiest solution. Unfortunately I don't have access to any Plesk to provide instructions, but you may try this.
I also found another possible solution which involves renaming the current domain and adding back the domain. Do remember to make backup of your files and database before attempting this.
And last resort would be the solution you suggested. Good luck!
Related
I want to keep the all the file structure of extension when we uninstall any extension from the site.
In the uninstall process I want to remove DB tables only and want to keep all Files/Folders.
Can you please guide me if there is any solution.
Thanks
The manifest file for the extension includes a list of the relevant files that are installed for the extension. These can be copied from the website and zipped to recreate the install file for the extension.
Some extensions may also create associated data which you can back up by exporting relevant database tables and/or files (e.g. in the media or images folders).
A normal uninstall process (via Joomla! manage form) removes everything unless the extension has bug in its uninstall schedule. So, if you need to keep the files, uninstalling the extension won't be a good idea. I suggest you drop tables via phpMyAdmin instead.
To do that, go to your web hosting control panel (cPanel, DirectAdmin etc.) and look for the link to phpMyAdmin. Then select the database that contains your website data (if you got multiple databases and are not sure which one is the right one, you can check it via Joomla! admin > Global Configuration). When you found the database in phpMyAdmin, click on its name to go to its tables. Then select the table(s) of that specific extension by checking the checkbox(es) beside them. Then at the bottom of the all tables click "Drop". In the popup window click "OK" and the table(s) will be removed without effecting your folders/files.
I suggest you get a backup of your whole website first, if you're new to phpMyAdmin.
Be careful!
I've come across a strange kind of a bug or issue after updating my MODx Revo 2.2.15-pl to MODx Revo 2.3.0-pl
The right side of the admin panel just disappeared after modx revo update
However, if I install a fresh copy of MODX from scratch, this problem doesn't appear at all.
I have updated my site several times before without problems. I always followed the steps described in the official manual Upgrading MODX Revolution 2.x
Maybe someone familiar with this situation can help me find out what's wrong?
Also be careful with .htaccess in root MODx folder, try not change him, in some cases it causes issues. MODX Revo bug.
I find this is generally a symptom due to permissions on the /assets/ directory
make sure the webserver has permission to read/write to /assets/components/ [and /manager/ and /connectors/]
clear cache [always!]
disable js/css compression
make sure that the left panel is not actually collapsed [older versions was difficult to see the little arrow!]
Errors/problems should show up in core/cache/logs/ installation log.
Anyway, probably what has happened here is that you uploaded all your files VIA ftp as the ftp user & the webserver cannot overwrite those files. To make life easier on you, use the advanced install - that way all you have to upload are the /setup/ and /core/ directories [both should be read/write by the webserver as well]
I have an ASP.Net application which uses Fedlet from Oracle. It's all working but I want to move the configuration from the App_Data folder to App_Data\Fedlet since we have all our configurations and extensions sitting in the App_Data (in neatly organised subfolders).
I've checked the Fedlet.dll.config file, but can't find any way to maybe reconfigure the folder but if there's any place to change it, I'm going to guess that's the place to change it.
Any pointers would be much appreciate as I've been searching for hours
Since I haven't found any answers anywhere on the net regarding this and since I managed to guess my way through, I decided to post the answer here for future reference both for myself and others.
If you place your web pages into a subfolder (example /pages/) then just place an app_data folder into the new folder (example /pages/app_data/) an
Is there any way to change Netbeans (7.0.1) cache directory?
I'm just wonna change directories of cache/temp for few apps... and one of them is NetBeans...
It seems this is not possible for Netbeans 7 (unless you relocate the whole userdir or create links as suggested by #MadWizard).
Fortunately, it seems this will be possible in Netbeans 7.1 by using the new --cachedir command-line option: http://wiki.netbeans.org/FaqAlternateUserdir
Quoting http://platform.netbeans.org/articles/installation.html
It is not reasonable to share this directory between different Products - the cache would be useless, the logs would get confusing and also the user modifications to the config would could be ambiguous. That is why each Product shall define its own directory prefix (based on its name) and pass it into the general nbexec command (for example using the --defaultuserdir parameter). The user can override the default during invocation of the the product launcher (e.g. nbweb --userdir myuserdir).
Review documentation pointed by me. If it does not help, you may consider using links, ie. create cache dir where desired and then within netbeans directory structure (described by the page) create link pointing to prepared cache.
Sometimes when we issue an upgrade to our application we need to install some files to the application's Data folder. We want to make it possible for the users to move this folder to a place of their liking. But how to deal with this at install time?
I was thinking of deploying to the user's AppData folder and have the application somehow check there for new files at startup.
Any advice or references would be very welcome!
We use InnoSetup for a VB6 application if that matters for your answer.
Generally the best solution I've found is to allow the user to move the folder from within the application.
This allows the application to keep track of where its data is being kept (by adding a reference to it in a file or registry entry which it accesses at load time) and to access it seamlessly in the future.
Your update routines can then also access this information to determine where to place the update files.
Alternatively, make sure the folder name is as distinctive as possible and add a search routine to look for the directory in a number of sensible places at load time. Then write your manual specifying that the data folder can be moved to one of those locations ONLY.
Wouldn't the users just run an update or patch package? I'm not sure why they'd want or need to see such files. It's pretty rare for commercial software to offer users the options of where to store program settings and other internal-use files.
Give some thought to this before putting a lot of stuff into users' roaming profiles. You might want LocalAppData instead.