Quantcast
Channel: Installing and upgrading help
Viewing all 47009 articles
Browse latest View live
↧

Re: Profiles images not working. Slasharguments? mod_fcgid?

June 3, 2015, 12:47 pm
$
0
0
by Matteo Scaramuccia.  

Hi San,
filepath and filename are part of the metadata of a file, both registered into the database while the physical stream of bytes is stored within the DATAROOT under the folder filedir in a 2-level folders hierarchy based on the first chars of its hash: read the details in https://docs.moodle.org/dev/File_API_internals#File_storage_on_disk.

You should start searching the raw files under the filedir to look if there they are broken too: if yes, than the scaling process fails and you should find traces of some errors in the error log file of your web server / PHP stack. It could be possible that no error will be shown to the end user due the warning suppressor set here: https://github.com/moodle/moodle/blob/MOODLE_29_STABLE/lib/filestorage/stored_file.php#L1045. Remove "@" and try uploading a different profile image to trigger the a new scaling process.

Then try to remove "preview=thumb&" to see if a valid file will be downloaded: if yes than GD is someway the culprit.

It's difficult to show you the exact path to debug this issue since there are multiple places where the code could break in your environment.

HTH,
Matteo

↧
Search

Re: Required parameter (sesskey) was missing

June 4, 2015, 9:10 am
$
0
0
by GME GME.  

Hi, I had the same error message on my installation. I checked my upload size limit and it was 128M but still the error ocurred. When I changed the permission to moodle folder to read/write, the error stopped.

So you  can try it and see. It should work for you.

↧
↧

Re: Problem upgrading from 2.6.1 to 2.9 (different OS and DB)

June 4, 2015, 9:11 am
$
0
0
by Howard Miller.  

Assuming your database is running....

Your GRANT command doesn't match what you put in your config.php in some respect. If the web server and database are on different machines (hostname is something other than 'localhost') I would repeat the GRANT with the IP if you used the hostname - or vice versa. 

Mariadb is fully compatible with MySQL so it won't be that. 

↧

Re: Upgrading PHP and MySQL

June 4, 2015, 10:37 am
$
0
0
by Bret Miller.  

I am running Moodle 2.7 and 2.8 the latest PHP 5.5.x and MySQL 5.5.x. I wouldn't think you'd have problems with the latest PHP and MySQL and I would probably try it. I would also probably try it on a test server before upgrading my live server just in case it caused issues.

↧

Re: Profiles images not working. Slasharguments? mod_fcgid?

June 4, 2015, 10:41 am
$
0
0
by Matteo Scaramuccia.  

Eh eh smile.

At the end, you've learned more than something about the Moodle internals.

Have a nice day,
Matteo

↧
↧

Re: Moodle 2.6.1 Site Blank Page

June 4, 2015, 11:01 am
$
0
0
by annahtreek ihtoj.  

Hi Howard Miller,

Thanks for the help. I deleted the codes I added in config.php and  uncommented  section 7 of my config-dist.php like this

//=========================================================================

// 7. SETTINGS FOR DEVELOPMENT SERVERS - not intended for production use!!!

//=========================================================================

//

// Force a debugging mode regardless the settings in the site administration

@error_reporting(E_ALL | E_STRICT); // NOT FOR PRODUCTION SERVERS!

@ini_set('display_errors', '1');    // NOT FOR PRODUCTION SERVERS!

$CFG->debug = (E_ALL | E_STRICT);   // === DEBUG_DEVELOPER - NOT FOR PRODUCTION SERVERS!

$CFG->debugdisplay = 1;             // NOT FOR PRODUCTION SERVERS!

//

// You can specify a comma separated list of user ids that that always see

// debug messages, this overrides the debug flag in $CFG->debug and $CFG->debugdisplay

// for these users only.

$CFG->debugusers = '2';

//

// Prevent theme caching

$CFG->themedesignermode = true; // NOT FOR PRODUCTION SERVERS!

//

// Prevent JS caching

$CFG->cachejs = false; // NOT FOR PRODUCTION SERVERS!

//

// Restrict which YUI logging statements are shown in the browser console.

// For details see the upstream documentation:

//   http://yuilibrary.com/yui/docs/api/classes/config.html#property_logInclude

//   http://yuilibrary.com/yui/docs/api/classes/config.html#property_logExclude

$CFG->yuiloginclude = array(

     'moodle-core-dock-loader' => true,

     'moodle-course-categoryexpander' => true,

);

$CFG->yuilogexclude = array(

     'moodle-core-dock' => true,

     'moodle-core-notification' => true,

);

//

// Set the minimum log level for YUI logging statements.

// For details see the upstream documentation:

//   http://yuilibrary.com/yui/docs/api/classes/config.html#property_logLevel

$CFG->yuiloglevel = 'debug';

//

// Prevent core_string_manager application caching

$CFG->langstringcache = false; // NOT FOR PRODUCTION SERVERS!

//

// When working with production data on test servers, no emails or other messages

// should ever be send to real users

$CFG->noemailever = true;    // NOT FOR PRODUCTION SERVERS!

//

// Divert all outgoing emails to this address to test and debug emailing features

$CFG->divertallemailsto = 'root@localhost.local'; // NOT FOR PRODUCTION SERVERS!

//

// Uncomment if you want to allow empty comments when modifying install.xml files.

$CFG->xmldbdisablecommentchecking = true;    // NOT FOR PRODUCTION SERVERS!

//

// Since 2.0 sql queries are not shown during upgrade by default.

// Please note that this setting may produce very long upgrade page on large sites.

$CFG->upgradeshowsql = true; // NOT FOR PRODUCTION SERVERS!

//

// Add SQL queries to the output of cron, just before their execution

$CFG->showcronsql = true;

//

// Force developer level debug and add debug info to the output of cron

$CFG->showcrondebugging = true;

I still see only a Blank page. What am I doing wrong?

↧

Re: Moodle 2.6.1 Site Blank Page

June 4, 2015, 11:35 am
$
0
0
by Howard Miller.  

Just checking - you copied those lines across to config.php (config-dist.php does nothing and is for reference only)?

Have you checked in your web server's error log?

↧

Re: Problem upgrading from 2.6.1 to 2.9 (different OS and DB)

June 4, 2015, 12:01 pm
$
0
0
by Marius Jugariu.  

Hi Howard,

Thanks for your reply. The database is running. The database and web server are on the same machine, the hostname is localhost. I have checked and there are appropriate permissions for database and folder access.

Still can't figure what the problem might be ;(

↧
Search

Re: Upgrading PHP and MySQL

June 4, 2015, 12:18 pm
$
0
0
by Jon Witts.  

There is no need to upgrade your MySQL... 23 is greater than 3!

Jon

↧
↧

Re: Plugins check moodle 2.7

June 4, 2015, 12:46 pm
$
0
0
by Johnny Praxis.  

Hi Mikhail and Albert

I guess you two are not the only ones with that issus so here is the fix.

Write this command to list the problematic tables: php admin/cli/mysql_compressed_rows.php -l

Convert them with this command (as the root user): php admin/cli/mysql_compressed_rows.php -f

If it doesn't work you could run this command to show the DB commands:php admin/cli/mysql_compressed_rows.php -s

The previous command should display something like this:USE yourtable;SET SESSION sql_mode=STRICT_ALL_TABLES;SET GLOBAL innodb_file_per_table=1;SET GLOBAL innodb_file_format=Barracuda;ALTER TABLE mdl_data ROW_FORMAT=Compressed;ALTER TABLE mdl_data_fields ROW_FORMAT=Compressed;ALTER TABLE mdl_enrol_paypal ROW_FORMAT=Compressed;ALTER TABLE mdl_lti ROW_FORMAT=Compressed;ALTER TABLE mdl_user ROW_FORMAT=Compressed;ALTER TABLE mdl_user_info_field ROW_FORMAT=Compressed;

Just run that code in phpMyAdmin or a similar admin tool to fix the tables. Remember to create a backup before you do that smile

↧

Re: Problem upgrading from 2.6.1 to 2.9 (different OS and DB)

June 4, 2015, 12:52 pm
$
0
0
by Ken Task.  

Pardon intrusion ...

In CentOS 6.6 does it still use SELinux?   In the past, SELinux on by default.   Might set from enforcing to 'permissive'.

cd /etc/selinux

nano config

# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
#    enforcing - SELinux security policy is enforced.
#    permissive - SELinux prints warnings instead of enforcing.
#    disabled - SELinux is fully disabled.
SELINUX=permissive <--- CHANGE THIS

Reboot box and watch the boot up for any issues dealing with SELinux.

Also, localhost DB should be using mysqli (see the 'i' on the end of that?).   It's not connecting to the MySQL port, but rather, it should be using a 'socket' connection to the DB.


$CFG->dbtype    = 'mysqli';

From a terminal session on the server, see if you can connect to the DB as the same user you have set in config.php of Moodle using the same password in the config.php:

mysql -u [moodleuser] -p[moodleuserpassword]

And, as Howard as already mentioned, does that user have the permissions it needs to run Moodle?

Gonna put a plug in here for git.   Hope you installed the 2.9 using git.   That will make your Moodle/OS admin role much much much easier.  My 2 cents, of course.

'spirit of sharing', Ken


↧

Re: How long does it take to upgrade the database?

June 4, 2015, 10:33 pm
$
0
0
by kishore K.  

Hi thanks Just but when I am going to install this I got the error in installation process (DDL error).installation done before i got this error message.Could I know why this error is coming and I had given current paths and web root and every thing. But till  I am facing the same issue while installation period.

↧

Re: Problem upgrading from 2.6.1 to 2.9 (different OS and DB)

June 5, 2015, 1:28 am
$
0
0
by Marius Jugariu.  

Thank you both, Ken and Howard.

SELINUX It is already set to "enforcing". I changed it to permissive and restarted it to see if it makes a difference but no joy so I changed it back to enforcing, the way it was.

Yes, I am able to connect to the database via SSH (with Putty) and execute commands so the database is definitely working. I can also see all the tables, etc. from phpmyadmin.

In config.php I have it as:

<?php  // Moodle configuration file
 
unset($CFG);
global $CFG;
$CFG = new stdClass();
 
$CFG->dbtype    = 'mariadb';
$CFG->dblibrary = 'native';
$CFG->dbhost    = 'localhost';
$CFG->dbname    = '[content]';
$CFG->dbuser    = 'root';
$CFG->dbpass    = '[content]';
$CFG->prefix    = 'mdl_';
$CFG->dboptions = array (
  'dbpersist' => 0,
  'dbsocket' => 1,
);
 
$CFG->wwwroot   = '[content]';
$CFG->dataroot  = '/var/www/moodledata';
$CFG->admin     = 'admin';
 
$CFG->directorypermissions = 0777;
 
$CFG->passwordsaltmain = '[content]';
 
require_once(dirname(__FILE__) . '/lib/setup.php');


libxml_disable_entity_loader(false);
 
// There is no php closing tag in this file,
// it is intentional because it prevents trailing whitespace problems!


Any other thoughts? sad

↧
↧

Re: Upgrading PHP and MySQL

June 5, 2015, 1:34 am
$
0
0
by Nick Varney.  

My mistake Jon, I missed off a digit. 

Moodle 2.7 and above requires 5.5.31. We are on 5.5.23


↧

Re: Problem upgrading from 2.6.1 to 2.9 (different OS and DB)

June 5, 2015, 2:12 am
$
0
0
by Howard Miller.  

"You are 100% correct, Howard"

Not according to my wife wink

↧
Search

Missing component "questionnaire"

June 5, 2015, 4:17 am
$
0
0
by curt bixel.  

I seem to have successfully restored my courses to a new server.  My old server was running 2.6.   The new server is running 2.9.


When restoring the courses with full developer debugging, I get the following predictable error message indicating that the questionnaire plugin has not been installed.  (The questionnaire is not yet available for 2.9.)  Will this cause any issue with my restore?


Invalid get_string() identifier: 'pluginname' or component 'questionnaire'. Perhaps you are missing $string['pluginname'] = ''; in mod/questionnaire/lang/en/questionnaire.php?

  • line 349 of /lib/classes/string_manager_standard.php: call to debugging()
  • line 6656 of /lib/moodlelib.php: call to core_string_manager_standard->get_string()
  • line 173 of /backup/util/ui/renderer.php: call to get_string()
  • line 383 of /backup/util/ui/restore_ui_stage.class.php: call to core_backup_renderer->backup_details()
  • line 127 of /backup/restore.php: call to restore_ui_stage_confirm->display()

↧

Re: Missing component "questionnaire"

June 5, 2015, 5:00 am
$
0
0
by Howard Miller.  

I think you'd be unlucky if the 2.8 version doesn't work on 2.9!

↧
↧

Re: Site Administration and other links not working

June 5, 2015, 5:56 am
$
0
0
by Laura Amorocho.  

Thanks Chris, only after I purged caches i was able to see the changes.. All working smoothly now. Thanks to all smile

↧

Re: Problem upgrading from 2.6.1 to 2.9 (different OS and DB)

June 5, 2015, 6:12 am
$
0
0
by Ken Task.  

Add the debug lines to the config.php file.

Still think SELinux might be involved there.  Did you check your secure/apache error logs to see if there were any references to SELinux allowing in permissive mode that would also indicate it would deny if it were enforcing?

Ok ... I know others might dis-agree, but ... you are trying to not only move but upgrade in one step.

Might be a little more work but think it best to move the site you've got first to the new server.   That is easier to do as 1st step.   You need a copy of the data directory and an sql dump and the config.php file of the 2.6.x.   On the new server use git to acquire the latest 2.6.x code, move your config.php file into the new code directory - edit config.php for new server.  NOTE: if the URL is going to change then one needs to search/replace for http://oldsite/ replace with http://newsite/.   In other words, get the old site to the new server up and running.   That will result in a minor update of the site.

Do a full site backup once you get it working.   This becomes the fall back point should any steps upwards fail.

Then, using git, march it upwards to 2.7.highest.   At that point, stop ... check the site for errors.   Get updates to plugins etc..    Working?  OK, another full site backup ... that backup now becomes the fall back point.

Then, using git again, march it upwards to 2.8.highest.

Know that takes longer but have found that there are fewer issues lurking for later discovery.

'spirit of sharing', Ken


↧

Re: Missing component "questionnaire"

June 5, 2015, 7:00 am
$
0
0
by AL Rachels.  

Hi Curt,

The current version of Questionnaire works just fine for me in the latest Moodle 2.9. If you turn on debugging it will give one warning:

Function moodleform_mod::add_intro_editor() is deprecated, use moodleform_mod::standard_intro_elements() instead.

The warning will not stop you from using questionnaire as it is, but the fix until a new version comes out is very simple.

in ..../mod/questionnaire/mod_form.php change line 44 from: $this->add_intro_editor(false, get_string('description'));

So that it is now: $this->standard_intro_elements(false, get_string('description'));

Seems like this change is going to be needed for any add-on when creating a new activity that uses a mod_form.php file. All the built-in/core activities and resources that I've checked have already been modified.

HTH,

AL


↧
Viewing all 47009 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>