I am unable to install the following question types with my moodle
1. Drag and drop into text (qtype_ddwtos)
2. Drag and drop matching (qtype_ddmatch)
I am using I am using Moodle 2.5.4 (Build: 20140113), php 5.4.7, MySQL 5.5.27, Apache 2.4.3, XAMPP server version 1.8.1
I have downloaded the plugins and unzip it then placed in the moodle->question->type. After that if I click the notifications link it is showing only blank page. Please advise me how to go further and how to resolve this issue and make use of those plugins.
the idea is to give the 755 permission to the "ddmatch" and "ddwtos" folders.
1- copy the two folder to moodle->question->type (as you did)
2- cd to this this directory:
cd /opt/lampp/htdocs/moodle/question/type
3- and change the permission of the two folder:
sudo chmod -R 755 ddwtos ddmatch
it worked for me !
I just checked out 2.5.4 and downloaded the plugins you mentioned - making sure they were both 2.5 versions - and extracted them into /question/type
https://moodle.org/plugins/view.php?plugin=qtype_ddmatch
https://moodle.org/plugins/view.php?plugin=qtype_ddwtos
Then went to notifications, they both require other plugins
qtype_match doesn't exist unfortunately
https://moodle.org/plugins/view.php?plugin=qtype_match
However gapselect does, so I downloaded that one too
https://moodle.org/plugins/view.php?plugin=qtype_gapselect
Then ran the upgrade and no errors were shown.
Is this on linux? Its possible that the extracted files haven't got the correct permissions - check the ownership of the folders : http://docs.moodle.org/25/en/Security_recommendations#Running_Moodle_on_a_dedicated_server
I would also double check that the files have been unzipped into the correct folder - so you should have /question/type/ddmatch, /question/type/ddwtos and /question/type/gapselect
If all that is okay then, like davosmith says, if you can switch on debugging and paste the error here. If you can't get into the system then edit /config.php and add these 2 lines after $CFG = new stdClass();
$CFG->debug = 32767;
$CFG->debugdisplay = 1;
Then try going to notifications again and see what the error is /admin/index.php
Related
I've downloaded the sources for kdesvn from the github repo as I'm thinking to look into working on an addition to the project. Now turns out, I'm not even able to properly compile the downloaded sources: I've created a directory kdesvn-build changed into it and launched cmake ../ (as described on https://github.com/KDE/kdesvn/blob/master/INSTALL-cmake) which does some stuff but then stops saying:
CMake Error: The following variables are used in this project, but
they are set to NOTFOUND. Please set them or make sure they are set
and tested correctly in the CMake files: SUBVERSION_INCLUDE_DIR
Now, I don't know what SUBVERSION_INCLUDE_DIR should be set to nor could I find it searching around the web. Anyone?
It is a directory containing svn_*.h files. If you are on Linux, you'd need to install something like subversion-dev package. On FreeBSD headers are installed with main package, and the directory is /usr/local/include/subversion-1/.
When I compile static with php bin/magento setup:static-content:deploy, I'm getting the following errors:
Unable to get content for 'frontend/Magento/blank/en_US/css/source/lib/_lib.less'
Unable to get content for 'frontend/Magento/luma/en_US/css/source/lib/_lib.less'
I was also facing the same issue. Then I went through the comments from different people on GitHub here. After that I was able to fix by recovering the folder "lib/web/css" or whole "lib/web" under root directory.
Lastly run the command and there was no error :
bin/magento setup:static-content:deploy en_US -f
Based on your setup version you can take it from here : https://github.com/magento/magento2/tree/2.3/lib
Your Magento probably was poorly updated, you might be able to fix it by getting a new composer installation in the same version and replacing your lib folder with a clean lib folder from the native installation.
I have downloaded a theme for moodle and i tried to add it to the existing themes using method B in the following link(using plugin).
https://www.vidyamantra.com/sales/index.php?/Knowledgebase/Article/View/242/0/how-to-install-new-theme-in-moodle
as per the steps the theme got updated in the plugin list but it is not visible in the themes(no change in available theme) so that i could not change my moodle theme.
so,please help me to resole this..
This is a common issue. Certain servers (depending on how they're configured and what version of PHP is installed) will not parse the theme's PHP files correctly.
If you find that you're uploading themes via the front-end and they're not coming up, you will need to upload via FTP/cPanel (Method A).
Try Using FTP, I use WinSCP (windows) then locate the "theme" folder.
"/var/www/html/yourMoodle/theme"
upload "yourTheme.zip" to this folder.
the using ssh unzip the file. (ubuntu)
usr$ sudo unzip /var/www/html/yourMoodle/theme/yourTheme.zip && sudo rm yourTheme.zip
then go to your moodle and change the theme
Unzip the downloaded theme and put it under theme/ directory. Run the upgrade from cli
cd admin/cli/
php upgrade.php
You should see it under theme when you login as administrator.
I am currently using Magento community edition, version 1.7.0.0, and as recommended by Magento due to a major security loophole fix, I want to upgrade my application to use latest version, 1.7.0.2.
What is the best way to upgrade magento version?
I know there are ways like command-line upgrade and using Magento Connect Manager, but not sure which and how to use.
thanks
The easiest way is to go to the Magento Connect Manager and press the Check for Upgrades Button.
Then you can see updates for all versions.
If you want to Update all packages then take Mage_All_Latest
I think when you are in the same Major release the update should work without any problems.
If you get some trouble with dependencies. You can do an upgrade with your console:
./mage upgrade-all --force
After using force you should check all your functions.
Follow the below steps:
Download the latest magento version(say 1.9) from http://www.magentocommerce.com/download
Backup every thing
Now remove all files and folder from your site code(mine say 1.7) and put in a new folder say ‘x’ folder.Put maintenance flag and place all magento files from latest magento download folder.
Now from magento 1.7( ‘x’ folder) merge the following custom folders into 1.9
app/code/local
app/code/community
Media
Your theme or package (app/design/frontend/default/<your theme> or app/design/frontend/<your package>)
Folders from Skin (both for adminhtml and frontend).
Copy app/etc/modules/ to current app/etc/modules/ from ‘x’ folder
Custom admin theme folder from adminhtml/default/yourtheme.
copy your custom folders from adminhtml/default/default/ (‘x’ folder) to adminhtml/default/default/ (1.9).
Custom js files from app/js/. from ‘x’ folder
Now go to app/etc/local.xml of 1.9 and put your database and password details
Remove maintenance.flag file and run your site on browser, and you are done
We're setting up an OpenSolaris server on Amazon's EC2 service. However, vi/vim doesn't work properly, and pkg doesn't have nano/pico.
Is there any other text-editor maybe?
Sounds like you may just need to set an appropriate termtype to get vi working. Look into the "TERM" environment variable options, perhaps one of those will help you.
You may try copying the nano binaries (or compiling the source), to your user account and running it from there. It worked for me in a similar situation.
Have you looked at http://www.sunfreeware.com/?
SUN is working on the SUNWgnu-nano package to include this in the next release. In the meantime, you can compile the nano sources yourself. It worked for me. To compile, follow these steps:
Make sure you install SUNWgcc package so that gcc is installed.
Download the source package from the debian distribution.
http://packages.debian.org/source/stable/nano
Unzip the package with 'gunzip xxxx.tar.gz' where xxxx.tar.gz is the source package you downloaded.
Untar the package with 'tar -xf xxxx' where xxxx is the unzipped source package.
Go to the source folder. Do a './configure' to create the make file for your system.
Type 'make' to create the binary
The 'nano' binary should be located in the src subfolder. Copy this to '/usr/bin'. And create a soft link for 'pico' to it i.e. 'ln -s /usr/bin/nano pico'
Test it out!
1) Open the Package Manager (System > Administration > Package Manager)
2) Open the Repository settings (Settings > Manage Repositories)
3) Add the Blastwave repository (Name: blastwave, URL: http://blastwave.network.com:10000 )
4) Select the repository in the upper right corner
5) Search for the package 'IPSnano'
6) Select the pacakge
7) Press 'Install/Update'
8) Modify your path to include /opt/csw/bin
(For example $ vi ~/.profile and then add the line above to your path)
9) Logout and in again to reflect the changes
Check whether the correct version of nano is used:
$ which nano
It looks like both Nano and Pico are available as auto-generated packages in the "pending" repository here: http://pkg.opensolaris.org/pending/en/index.shtml. I think they are waiting for someone to follow the verification steps and vouch that they work. Then they can be moved to the contrib repository. You can read more here: http://opensolaris.org/os/community/sw-porters/.