Elgg Block error after install

Elgg Block error after install

by Wei Tang -
Number of replies: 52

Hi,

After I finished installation of Elgg block, I can see "Join Now" button in my course. Also, I can see elgg register form after click "Join Now" button.

The problem is :

1. In the how to document for Elgg, there will be a latest activity list displayed in eportfolio block area after student registered in Elgg. But, there is still "Join Now" button.

2. When student click "Join now" button again, there will be redirected to Elgg install root but return a "Object id# xx".

Both Moodle and Elgg installed in same machine.

Thanks

Tang

Average of ratings: -
In reply to Wei Tang

Re: Elgg Block error after install

by Michaela Bell -
hi there,

i have the exact same problem - posted it twice in the other thread. is there really nobody who can help us? penny??

greets,
michi
In reply to Michaela Bell

Re: Elgg Block error after install

by Penny Leach -
Hi, it's pretty hard for me to diagnose this at a distance without a lot of information. Please make sure you post enough information so that I can help you.

Eg: a screenshot of your blocks settings page in moodle, and the snippet of config.php from your elgg.

Also, please bear this in mind. The moodle/elgg block is not just simple and straightforward to set up for everyone, and it is (on the moodle side at least) a nonstandard block. I'm really happy to try and help everyone get up and running but it's hard for me to do without the necessary information, especially with this volume.

Perhaps some of the people who are up and running with the moodle/elgg block can chime in and try and help out too.

In reply to Penny Leach

Re: Elgg Block error after install

by Michaela Bell -
hi penny,

this is the line from config.php:
 $CFG->lmshosts = array('moodle' => array('token' => 'gucci', 'confirmurl' => 'http://127.0.0.1/moodle/blocks/eportfolio/confirm.php', 'baseurl' => 'http://127.0.0.1/moodle', 'name' => 'moodle'));

and here is a screenshot of my moodle-settings:


thanks for your help!!
michi
In reply to Michaela Bell

Re: Elgg Block error after install

by dave cormier -
after reading the other comments below... i have another question... Is your elgg working properly? Have you been using it for a while or are you new to it? The php settings can be... a little interesting on the first install
In reply to Michaela Bell

Re: Elgg Block error after install

by Penny Leach -
I don't really understand exactly what the sequence of events is.

The block shows up, with 'join now' button. You click join now, fill in the registration form and then what?

The problem you're talking about is something that prints, Object id# x, right? But at exactly what stage? If you could write up exactly what you do and at what URL the problem is, and at what STAGE you're seeing it, that would be helpful.
In reply to Penny Leach

Re: Elgg Block error after install

by Will Taylor -
Penny,

I had a successful instal of Elgg/Moodle with the integration block on a test server, but am having difficulties now setting up my production installation, on a different server

Am using latest Moodle 1.6.1, latest Elgg 0.601, and block from the Moodle modules & plugins page, all downloaded 7/26.

On installing the block, although I get a "successful instal" message, this is preceeded by the following error text (which also appears above the block when it is placed on a page):

.x, // courtesy, Ryan Currie, ryan@digibliss.com if (!function_exists('array_change_key_case')) { define("CASE_UPPER",1); define("CASE_LOWER",0); function array_change_key_case($array,$case=CASE_LOWER) { if ($case=CASE_LOWER) $cmd=strtolower; elseif ($case=CASE_UPPER) $cmd=strtoupper; foreach($array as $key=>$value) { $output[$cmd($key)]=$value; } return $output; } } ?> ( MAGPIE_DEBUG ) { trigger_error( $errormsg, $lvl); } else { error_log( $errormsg, 0); } } function debug ($debugmsg, $lvl=E_USER_NOTICE) { if ( MAGPIE_DEBUG ) { $this->error("MagpieRSS [debug] $debugmsg", $lvl); } } } ?> unction is_error ($sc) { return $sc >= 400 && $sc < 600; } /*=======================================================================*\ Function: is_client_error Purpose: return true if Error status code, and its a client error \*=======================================================================*/ function is_client_error ($sc) { return $sc >= 400 && $sc < 500; } /*=======================================================================*\ Function: is_client_error Purpose: return true if Error status code, and its a server error \*=======================================================================*/ function is_server_error ($sc) { return $sc >= 500 && $sc < 600; } ?>

I can visit Elgg from Moodle once and set up account, but return of a registered user (the link still says "Join now!") just gets the single-word "Object" page that others have mentioned.

The token & installid are OK, baseurl's are identical, I've left the network address blank in both block settings and config file (tried this both blank & completed), & using cp copy method.

moodle is set up in a subdomain, elgg is in a subdirectory w/in the moodle root, separate databases on the same server.

Any ideas?

thanks,
Will

In reply to Will Taylor

Re: Elgg Block error after install

by Penny Leach -
no idea sorry. that error message seems to be magpie errors, which is what the elgg block uses to get rss from elgg...

although that error is really weird... it actually looks like code is being printed straight to the browser.
In reply to Penny Leach

Re: Elgg Block error after install

by Will Taylor -
Is anyone else seeing this with Moodle 1.6.1 & the Elgg eportfolio block?
Am wondering if it is compatibility issue with 1.6.1 - I get the same code when trying to install the RSS Client block.

- will
In reply to Will Taylor

Re: Elgg Block error after install

by Penny Leach -
Hrmmm... when I wrote the block I pretty much directly copied code from the rss client block, so it makes sense if one is broken they both are.

I checked cvs and from what I can see, neither magpie (rss fetcher) or snoopy (http retriever, used by magpie) have been updated recently.

This is very strange.

What about other differences between your two servers? php version, in particular?
In reply to Penny Leach

Re: Elgg Block error after install

by Will Taylor -
Penny,
I posted to an RSS client block thread -
this is apparently not a server issue, as an attempt to use either block (RSS client, Elgg block) on the OLD server, in a MOODLE 1.6.1 installation, have the same issue.  (i.e., on that server, the RSS client worked fine in MOODLE 1.5.3, and the Elgg block worked fine in MOODLE 1.6 - but neither work in MOODLE 1.6.1).
- will
In reply to Will Taylor

Re: Elgg Block error after install

by Penny Leach -
hrmm.. someone must have changed something in magpie... I'm really flat out right now but will look into this if I possibly can.
In reply to Penny Leach

Re: Elgg Block error after install

by Will Taylor -
Penny,

I replaced the MOODLE 1.6.1 lib/magpie directory, with the equivalent directory from the 1.5.4 release (which contains an earlier version of Magpie).  I no longer get the text printed above the ePortfolio block.

However, still problems - the Join link allows me to join Elgg - the Join form in Elgg is automatically populated with my full name & email address, so it apparently is accessing my MOODLE database - however the button in the ePortfolio block remains "Join", and subsequent clicks on it give me the blank page
http:// ... /elgg/lms/join.php
with only the word "Object" printed on it, as others have reported.

Has anyone figured out this "Object" thingy?

thanks,
Will
In reply to Will Taylor

Re: Elgg Block error after install

by Will Taylor -
Some further info re the blank "Object" page rec'd when a previously-registered users links from Moodle to Elgg via the ePortfolio block -

The otherwise blank page received displaying "Object" is:
.../elgg/lms/join.php

If I erase /lms/join.php from the address bar, and refresh to go to
/elgg ,

I find that I am actually being logged in to Elgg (having previously made sure to log out of Elgg after the initial registration).  I end up then in the appropriate Profile page, logged in as the intended user.

So what is not happening is:
- Moodle is not being sent the activity report from Elgg to replace the "Join" button;
- I'm not being re-directed from /lms/join.php to the Elgg recent activities page, even tho I'm being logged in to Elgg from the ePortfolio block link

Any insight into what might be happening here, & how to fix it?
I'd sure love to get this to work ...
(p.s. - this is with MOODLE 1.6.1 and Elgg 0.601, but using the Moodle /lib/magpie directory from Moodle 1.5.4 to avoid the above-block error mentioned previously - previously had no such issue with Moodle 1.6b4 / Elgg 0.6final).

- will
In reply to Will Taylor

Re: Elgg Block error after install

by Will Taylor -
Am wondering now if this might be an Elgg 0.601 issue?
I just took a working test installation of MOODLE 1.6b4 / Elgg 0.6final - integrating fine - and upgraded Elgg to 0.601
elgg/config.php was preserved in the upgrade, no changes
Now, clicking on the MOODLE ePortfolio block "activity" link takes me to an entirely blank page at
http://www.simillibus.org/elgg/_activity/
& if I edit the address bar to /elgg and return,
I find that I am not logged in

Prior to the Elgg upgrade 0.6final -> 0.601, all was working fine.

- will
In reply to Will Taylor

Re: Elgg Block error after install

by Nick Chater -
This may help, I was having roughly the same problem, then I noticed that the confirmurl in the config.php in elgg ended in confirm.php not config.php as suggested in the help guide on the eduforge site

i.e.:
'confirmurl' => 'http://www.your-site.org.uk/blocks/eportfolio/confirm.php'

and not:
'confirmurl' => 'http://www.your-site.org.uk/blocks/eportfolio/config.php'

As detailed at:
https://eduforge.org/wiki/wiki/nzvle/wiki?pagename=MoodleElggHOWTO

It worked for me....

Thanks Penny for your post!!
In reply to Nick Chater

Re: Elgg Block error after install

by Will Taylor -
Thanks, but that isn't it - had already caught that error in the documentation.
Is anyone using this block successfully with MOODLE 1.6.1 / Elgg 0.601 ?
I've been over & over settings &c. & tho able to initially register a user, returning users still get only the blank "Object" page.
In reply to Will Taylor

Re: Elgg Block error after install

by Luke Hudson -

Well, there do seem to be several different problems mentioned in this thread.

1. 'Object' or (in some cases) 'Object id# xx' text is printed out after clicking 'Join Now'

This is printed because there isn't good error reporting code on the Elgg side. It should be saying something like "User already exists". Basically the join now button sends a request to elgg to join up, and elgg checks the information and finds an existing user who matches that info. At this point it prints out the user object (which appears only as 'Object') and gives up.
   
2.    Join Now appearing even after joining Elgg

Now this bug is really what leads to the one above. This button is shown when eportfolio cannot get the RSS data from Elgg  for the logged-in Moodle user.

This can occur in the following cases:
   
  1. The user does not exist yet in Elgg (this is the desired behaviour)
  2. Elgg's networkaddress setting is not the correct IP of the moodle site.
  3. Elgg's installid setting is not the same as the eportfolio block's installid
  4. Elgg's 'token' is not the same as the eportfolio block token
  5. The block_eportfolio_baseurl setting is not the url of the elgg site
  6. Finally, if some other error occurs and no RSS is returned when the eportfolio block requests the file at (block_eportfolio_baseurl)/lms/rss.php       

Things to check:
In the Elgg directory, look at the file 'config.php'.  Near the end of the file should be something a bit like this: 
$CFG->lmshosts = array(
'moodlesiteid' => array(
'token' => 'elggmoodletoken',
'networkaddress' => '127.0.0.1',
'baseurl' => 'http://localhost/moodle',
'confirmurl' => 'http://localhost/moodle/blocks/eportfolio/confirm.php',
'name' => 'Moodle'
)
);
Now, login to your moodle site as an admin user and go to:
    Configuration -> Blocks -> eportfolio -> Settings
Check that the settings there match what you are using with Elgg.

Specifically:
  • make sure that block_eportfolio_token is the same value as 'token' above (eg. elggmoodletoken)
  • make sure that block_eportfolio_installid is the same value as the installid above (eg. moodlesiteid)
  • check block_eportfolio_baseurl is indeed the URL of your elgg installation
  • check that the 'confirmurl' above is correct for your Moodle site. 
Now this doesn't address all the problems mentioned in this thread, but I hope that it helps some of you.
In reply to Will Taylor

Re: Elgg Block error after install

by Bhupinder Singh -

Hello Will,

I have a similar problem to yours. Went through the same screen return after the successful login.

Using Daves code. Shows a text file output as invalid IP Address.  and the screen showing only word OBJECT .

Garry

In reply to Penny Leach

Re: Elgg Block error after install

by Juvenal Sahiri -
Hello Penny,
I've tried every possible thing to install elgg 6.73 on winxp. I am using xampplite where moodle, mediawiki and other applications are installed flawlessly. Have been installing all moodle modules without a problem. I am stuck with elgg in the sense that I get a 500 error. Have tried everything I could to allowoverride All in .htaccess and apache htpd config.
The apache error log keeps telling me that "[Fri Jan 12 00:40:39 2007] [alert] [client 127.0.0.1] C:/xampplite/htdocs/elgg/.htaccess: AllowOverride not allowed here

I've tried everything suggested in the various discussions forums, nothing worked. Thanks for your help. If you are using 6.73, your could send me your apache config and htaccess files if they work. Let me know also which version of elgg is working for you.

Below is the content of my htaccess file and httpd config:
.htaccess
<IfModule !mod_rewrite.c>
# ugly ugly hack to detect missing mod_rewrite
# RedirectMatch must be to an absolute destination, so forces 500 error...
ErrorDocument 500 "Elgg error: Apache does not have mod_rewrite loaded. Please check your apache setup."
RedirectMatch 302 .* index.php
</IfModule>

Options +FollowSymLinks

AllowOverride All

# Not really necessary, just to be clean
#php_flag short_open_tag off
# Forgot that anyone might still have this turned on
#php_flag register_globals off

<IfModule mod_rewrite.c>

RewriteEngine on

# If Elgg is in a subdirectory on your site, you might need to add a RewriteBase line
# containing the path from your site root to elgg's root. e.g. If your site is
# http://example.com/ and Elgg is in http://example.com/sites/elgg/, you might need
#

RewriteBase /community/

#
# here, only without the # in front.
#
# If you're not running Elgg in a subdirectory on your site, but still getting lots
# of 404 errors beyond the front page, you could instead try:
#
RewriteBase /=

RewriteRule ^([0-9\-]+)\.css$ _templates/css.php?template=$1

RewriteRule ^(.+)\/rssstyles.xsl$ _rss/styles.php?rssurl=$1&url=$1

RewriteRule ^([A-Za-z0-9]+)(\/)?$ profile/index.php?profile_name=$1
RewriteRule ^([A-Za-z0-9]+)\/tags(\/)?$ search/personaltags.php?profile_name=$1
RewriteRule ^(([A-Za-z0-9])[A-Za-z0-9]+)\/rss\/?$ _rss/static.php?username=$1&userref=$2&type=profile
RewriteRule ^([A-Za-z0-9]+)\/rss\/(.+)\/?$ profile/rss2.php?profile_name=$1&tag=$2

RewriteRule ^([A-Za-z0-9]+)\/newsclient\/?$ _rss/subscriptions.php?profile_name=$1
RewriteRule ^([A-Za-z0-9]+)\/newsclient\/all\/?$ _rss/index.php?profile_name=$1
RewriteRule ^([A-Za-z0-9]+)\/newsclient\/all\/skip=([0-9]+)$ _rss/index.php?profile_name=$1&feed_offset=$2

RewriteRule ^([A-Za-z0-9]+)\/feeds\/?$ _rss/subscriptions.php?profile_name=$1
RewriteRule ^([A-Za-z0-9]+)\/feeds\/all\/?$ _rss/index.php?profile_name=$1
RewriteRule ^([A-Za-z0-9]+)\/feeds\/all\/skip=([0-9]+)$ _rss/index.php?profile_name=$1&feed_offset=$2

RewriteRule ^([A-Za-z0-9]+)\/weblog\/?$ _weblog/index.php?weblog_name=$1
ReWriteRule ^([A-Za-z0-9]+)\/weblog\/skip=([0-9]+)$ _weblog/index.php?weblog_name=$1&weblog_offset=$2
RewriteRule ^([A-Za-z0-9]+)\/weblog\/archive\/?$ _weblog/archive.php?weblog_name=$1
RewriteRule ^([A-Za-z0-9]+)\/weblog\/archive\/([0-9]+)\/([0-9]+)\/?$ _weblog/archive_month.php?weblog_name=$1&year=$2&month=$3
RewriteRule ^([A-Za-z0-9]+)\/weblog\/friends\/?$ _weblog/friends.php?weblog_name=$1
ReWriteRule ^([A-Za-z0-9]+)\/weblog\/friends\/skip=([0-9]+)$ _weblog/friends.php?weblog_name=$1&weblog_offset=$2
RewriteRule ^(([A-Za-z0-9])[A-Za-z0-9]+)\/weblog\/rss\/?$ _rss/static.php?username=$1&userref=$2&type=weblog
RewriteRule ^([A-Za-z0-9]+)\/weblog\/rss\/(.+)\/?$ _weblog/rss2.php?weblog_name=$1&tag=$2&modifier=is
RewriteRule ^([A-Za-z0-9]+)\/weblog\/rssnot\/(.+)\/?$ _weblog/rss2.php?weblog_name=$1&tag=$2&modifier=not
RewriteRule ^[A-Za-z0-9]+\/weblog\/([0-9]+)\.html$ _weblog/view_post.php?post=$1

RewriteRule ^tag\/(.+)\/?$ search/all.php?tag=$1
RewriteRule ^rsstag\/(.+)\/?$ search/rss.php?tag=$1
RewriteRule ^tag\/(.+)/ecl\/?$ search/ecl.php?tag=$1

RewriteRule ^([A-Za-z0-9]+)\/friends\/?$ _friends/index.php?friends_name=$1
RewriteRule ^([A-Za-z0-9]+)\/foaf\/?$ _friends/foaf.php?friends_name=$1

RewriteRule ^([A-Za-z0-9]+)\/communities\/?$ _communities/index.php?friends_name=$1
RewriteRule ^community\/([0-9]+)\/?$ _communities/community.php?community_id=$1

RewriteRule ^([A-Za-z0-9]+)\/files\/?$ _files/index.php?files_name=$1
RewriteRule ^([A-Za-z0-9]+)\/files\/([0-9]+)\/?$ _files/index.php?files_name=$1&folder=$2
RewriteRule ^([A-Za-z0-9]+)\/files\/([0-9\-]+)\/([0-9]+)\/(.+)$ _files/download.php?files_name=$1&folder=$2&filename=$4&id=$3
RewriteRule ^(([A-Za-z0-9])[A-Za-z0-9]+)\/files\/rss\/?$ _rss/static.php?username=$1&userref=$2&type=files
RewriteRule ^([A-Za-z0-9]+)\/files\/rss\/(.+)\/?$ _files/rss2.php?files_name=$1&tag=$2

RewriteRule ^([A-Za-z0-9]+)\/icons\/([-0-9]+)\/?$ _icons/icon.php?id=$2
RewriteRule ^([A-Za-z0-9]+)\/icons\/([-0-9]+)\/([A-Za-z])\/([0-9]+)\/?$ _icons/icon.php?id=$2&constraint1=$3&size1=$4
RewriteRule ^([A-Za-z0-9]+)\/icons\/([-0-9]+)\/([A-Za-z])\/([0-9]+)\/([A-Za-z])\/([0-9]+)\/?$ _icons/icon.php?id=$2&constraint1=$3&size1=$4&constraint2=$5&size2=$6

RewriteRule ^([A-Za-z0-9]+)\/calendar\/rss\/?$ _calendar/rss.php?username=$1
RewriteRule ^([A-Za-z0-9]+)\/calendar\/rss\/(.+)\/?$ _calendar/rss.php?tag=$2
RewriteRule ^([A-Za-z0-9]+)\/calendar\/([0-9]+)\.html$ _calendar/view_events.php?event_id=$2
RewriteRule ^([A-Za-z0-9]+)\/calendar\/import\/?$ _calendar/ical_import.php
RewriteRule ^([A-Za-z0-9]+)\/calendar\/archive\/?$ _calendar/archive.php?username=$1
RewriteRule ^([A-Za-z0-9]+)\/calendar\/archive\/([0-9]+)\/([0-9]+)\/?$ _calendar/archive_month.php?username=$1&year=$2&month=$3

RewriteRule ^([A-Za-z0-9]+)\/calendar\/?$ _calendar/index.php?context=private
RewriteRule ^([A-Za-z0-9]+)\/calendar\/friends\/?$ _calendar/index.php?context=friends
RewriteRule ^([A-Za-z0-9]+)\/calendar\/communities\/?$ _calendar/index.php?context=communities

# Some blogging clients probe Wordpress or MoveableType endpoints,
# redirect them to the Elgg xml-rpc endpoint
#
RewriteRule xml-rpc.php _rpc/RPC2.php
RewriteRule mt/mt-xmlrpc.cgi _rpc/RPC2.php

</IfModule>

===============
#
# This is the main Apache HTTP server configuration file. It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.2/>; for detailed information.
# In particular, see
# <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>;
# for a discussion of each configuration directive.
#
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path. If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
# with ServerRoot set to "C:/xampplite/apache" will be interpreted by the
# server as "C:/xampplite/apache/logs/foo.log".
#
# NOTE: Where filenames are specified, you must use forward slashes
# instead of backslashes (e.g., "c:/apache" instead of "c:\apache").
# If a drive letter is omitted, the drive on which Apache.exe is located
# will be used by default. It is recommended that you always supply
# an explicit drive letter in absolute paths, however, to avoid
# confusion.
#

# ThreadsPerChild: constant number of worker threads in the server process
# MaxRequestsPerChild: maximum number of requests a server process serves
ThreadsPerChild 250
MaxRequestsPerChild 0

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# Do not add a slash at the end of the directory path. If you point
# ServerRoot at a non-local disk, be sure to point the LockFile directive
# at a local disk. If you wish to share the same ServerRoot for multiple
# httpd daemons, you will need to change at least LockFile and PidFile.
#
ServerRoot "C:/xampplite/apache"

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
#
#Listen 12.34.56.78:80
Listen 80

#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
#
# Example:
# LoadModule foo_module modules/mod_foo.so
#
LoadModule actions_module modules/mod_actions.so
LoadModule alias_module modules/mod_alias.so
LoadModule asis_module modules/mod_asis.so
LoadModule auth_basic_module modules/mod_auth_basic.so
#LoadModule auth_digest_module modules/mod_auth_digest.so
#LoadModule authn_anon_module modules/mod_authn_anon.so
#LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authn_file_module modules/mod_authn_file.so
#LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
#LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_user_module modules/mod_authz_user.so
#LoadModule autoindex_module modules/mod_autoindex.so # don't load because of mod_autoindex_color.so
#LoadModule bucketeer_module modules/mod_bucketeer.so
#LoadModule cache_module modules/mod_cache.so
#LoadModule disk_cache_module modules/mod_disk_cache.so
#LoadModule file_cache_module modules/mod_file_cache.so
#LoadModule mem_cache_module modules/mod_mem_cache.so
#LoadModule cern_meta_module modules/mod_cern_meta.so
#LoadModule charset_lite_module modules/mod_charset_lite.so
LoadModule cgi_module modules/mod_cgi.so
LoadModule dav_module modules/mod_dav.so
LoadModule dav_fs_module modules/mod_dav_fs.so
#LoadModule deflate_module modules/mod_deflate.so
LoadModule dir_module modules/mod_dir.so
#LoadModule dumpio_module modules/mod_dumpio.so
LoadModule env_module modules/mod_env.so
#LoadModule expires_module modules/mod_expires.so
#LoadModule ext_filter_module modules/mod_ext_filter.so
#LoadModule headers_module modules/mod_headers.so
#LoadModule ident_module modules/mod_ident.so
#LoadModule imagemap_module modules/mod_imagemap.so
LoadModule include_module modules/mod_include.so
LoadModule info_module modules/mod_info.so
LoadModule isapi_module modules/mod_isapi.so
LoadModule ldap_module modules/mod_ldap.so
#LoadModule logio_module modules/mod_logio.so
LoadModule log_config_module modules/mod_log_config.so
#LoadModule log_forensic_module modules/mod_log_forensic.so
LoadModule mime_module modules/mod_mime.so
#LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule negotiation_module modules/mod_negotiation.so
#LoadModule proxy_module modules/mod_proxy.so
#LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
#LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
#LoadModule proxy_connect_module modules/mod_proxy_connect.so
#LoadModule proxy_http_module modules/mod_proxy_http.so
#LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule rewrite_module modules/mod_rewrite.so
LoadModule setenvif_module modules/mod_setenvif.so
#LoadModule speling_module modules/mod_speling.so
LoadModule status_module modules/mod_status.so
#LoadModule unique_id_module modules/mod_unique_id.so
#LoadModule userdir_module modules/mod_userdir.so
#LoadModule usertrack_module modules/mod_usertrack.so
#LoadModule version_module modules/mod_version.so
#LoadModule vhost_alias_module modules/mod_vhost_alias.so
LoadModule ssl_module modules/mod_ssl.so

LoadModule autoindex_color_module modules/mod_autoindex_color.so
#LoadModule mysql_auth_module modules/mod_auth_mysql.so
#LoadModule auth_remote_module modules/mod_auth_remote.so
#LoadModule sspi_auth_module modules/mod_auth_sspi.so
#LoadModule log_sql_module modules/mod_log_sql.so
#LoadModule log_sql_mysql_module modules/mod_log_sql_mysql.so
#<IfModule ssl_module>
# LoadModule log_sql_ssl_module modules/mod_log_sql_ssl.so
#</IfModule>
#LoadModule proxy_html_module modules/mod_proxy_html.so
#LoadModule xmlns_module modules/mod_xmlns.so
#LoadModule proxy_xml_module modules/mod_proxy_xml.so
#LoadModule bw_module modules/mod_bw.so

# 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition. These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#

#
# ServerAdmin: Your address, where problems with the server should be
# e-mailed. This address appears on some server-generated pages, such
# as error documents. e.g. admin@your-domain.com
#
ServerAdmin admin@localhost

#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
#
ServerName localhost:80

#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot "C:/xampplite/htdocs"

#
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
#
# First, we configure the "default" to be a very restrictive set of
# features.
#
<Directory />
Options FollowSymLinks
AllowOverride All
Order deny,allow
Deny from all
</Directory>

#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#

#
# This should be changed to whatever you set DocumentRoot to.
#
<Directory "C:/xampplite/htdocs">
#
# Possible values for the Options directive are "None", "All",
# or any combination of:
# Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
#
# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.
#
# The Options directive is both complicated and important. Please see
# http://httpd.apache.org/docs/2.2/mod/core.html#options
# for more information.
#
Options Indexes FollowSymLinks Includes ExecCGI

#
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be "All", "None", or any combination of the keywords:
# Options FileInfo AuthConfig Limit
#
AllowOverride All

#
# Controls who can get stuff from this server.
#
Order allow,deny
Allow from all

</Directory>

#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
<IfModule dir_module>
DirectoryIndex index.php index.php4 index.php3 index.cgi index.pl index.html index.htm index.shtml index.phtml
</IfModule>

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<FilesMatch "^\.ht">
Order allow,deny
Deny from all
</FilesMatch>

#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog logs/error.log

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

<IfModule log_config_module>
#
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
#
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common

<IfModule logio_module>
# You need to enable mod_logio.c to use %I and %O
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
</IfModule>

#
# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a <VirtualHost>
# container, they will be logged here. Contrariwise, if you *do*
# define per-<VirtualHost> access logfiles, transactions will be
# logged therein and *not* in this file.
#
CustomLog logs/access.log common

#
# If you prefer a logfile with access, agent, and referer information
# (Combined Logfile Format) you can use the following directive.
#
#CustomLog logs/access.log combined
</IfModule>

<IfModule alias_module>
#
# Redirect: Allows you to tell clients about documents that used to
# exist in your server's namespace, but do not anymore. The client
# will make a new request for the document at its new location.
# Example:
# Redirect permanent /foo http://www.example.com/bar

#
# Alias: Maps web paths into filesystem paths and is used to
# access content that does not live under the DocumentRoot.
# Example:
# Alias /webpath /full/filesystem/path
#
# If you include a trailing / on /webpath then the server will
# require it to be present in the URL. You will also likely
# need to provide a <Directory> section to allow access to
# the filesystem path.

#
# ScriptAlias: This controls which directories contain server scripts.
# ScriptAliases are essentially the same as Aliases, except that
# documents in the target directory are treated as applications and
# run by the server when requested rather than as documents sent to the
# client. The same rules about trailing "/" apply to ScriptAlias
# directives as to Alias.
#
ScriptAlias /cgi-bin/ "C:/xampplite/cgi-bin/"

</IfModule>

<Directory "C:/Xampplite/htdocs/moodle/mod/ipodcast">
AllowOverride All
</Directory>

#
# "C:/xampplite/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "C:/xampplite/cgi-bin">
AllowOverride All
Options None
Order allow,deny
Allow from all
</Directory>

#
# Apache parses all CGI scripts for the shebang line by default.
# This comment line, the first line of the script, consists of the symbols
# pound (#) and exclamation (!) followed by the path of the program that
# can execute this specific script. For a perl script, with perl.exe in
# the C:\Program Files\Perl directory, the shebang line should be:

#!c:/program files/perl/perl

# Note you _must_not_ indent the actual shebang line, and it must be the
# first line of the file. Of course, CGI processing must be enabled by
# the appropriate ScriptAlias or Options ExecCGI directives for the files
# or directory in question.
#
# However, Apache on Windows allows either the Unix behavior above, or can
# use the Registry to match files by extention. The command to execute
# a file of this type is retrieved from the registry by the same method as
# the Windows Explorer would use to handle double-clicking on a file.
# These script actions can be configured from the Windows Explorer View menu,
# 'Folder Options', and reviewing the 'File Types' tab. Clicking the Edit
# button allows you to modify the Actions, of which Apache 1.3 attempts to
# perform the 'Open' Action, and failing that it will try the shebang line.
# This behavior is subject to change in Apache release 2.0.
#
# Each mechanism has it's own specific security weaknesses, from the means
# to run a program you didn't intend the website owner to invoke, and the
# best method is a matter of great debate.
#
# To enable the this Windows specific behavior (and therefore -disable- the
# equivilant Unix behavior), uncomment the following directive:
#
#ScriptInterpreterSource registry
#
# The directive above can be placed in individual <Directory> blocks or the
# .htaccess file, with either the 'registry' (Windows behavior) or 'script'
# (Unix behavior) option, and will override this server default option.
#

#
# DefaultType: the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value. If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
DefaultType text/plain

<IfModule mime_module>
#
# TypesConfig points to the file containing the list of mappings from
# filename extension to MIME-type.
#
TypesConfig conf/mime.types

#
# AddType allows you to add to or override the MIME configuration
# file specified in TypesConfig for specific file types.
#
#AddType application/x-gzip .tgz
#
# AddEncoding allows you to have certain browsers uncompress
# information on the fly. Note: Not all browsers support this.
#
#AddEncoding x-compress .Z
#AddEncoding x-gzip .gz .tgz
#
# If the AddEncoding directives above are commented-out, then you
# probably should define those extensions to indicate media types:
#
AddType application/x-compress .Z
AddType application/x-gzip .gz .tgz

#
# AddHandler allows you to map certain file extensions to "handlers":
# actions unrelated to filetype. These can be either built into the server
# or added with the Action directive (see below)
#
# To use CGI scripts outside of ScriptAliased directories:
# (You will also need to add "ExecCGI" to the "Options" directive.)
#
AddHandler cgi-script .cgi

# For files that include their own HTTP headers:
#AddHandler send-as-is asis

# For server-parsed imagemap files:
#AddHandler imap-file map

# For type maps (negotiated resources):
#AddHandler type-map var

#
# Filters allow you to process content before it is sent to the client.
#
# To parse .shtml files for server-side includes (SSI):
# (You will also need to add "Includes" to the "Options" directive.)
#
AddType text/html .shtml
AddOutputFilter INCLUDES .shtml
</IfModule>

#
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type. The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#
#MIMEMagicFile conf/magic

#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
#

#
# EnableMMAP and EnableSendfile: On systems that support it,
# memory-mapping or the sendfile syscall is used to deliver
# files. This usually improves server performance, but must
# be turned off when serving from networked-mounted
# filesystems or if support for these functions is otherwise
# broken on your system.
#
EnableMMAP off
EnableSendfile off

# Supplemental configuration
#
# The configuration files in the conf/extra/ directory can be
# included to add extra features or to modify the default configuration of
# the server, or you may simply copy their contents here and change as
# necessary.

# xampplite specific settings
Include conf/extra/httpd-xampp.conf

# Server-pool management (MPM specific)
# Include conf/extra/httpd-mpm.conf

# Multi-language error messages
Include conf/extra/httpd-multilang-errordoc.conf

# Fancy directory listings
Include conf/extra/httpd-autoindex.conf

# Language settings
Include conf/extra/httpd-languages.conf

# User home directories
Include conf/extra/httpd-userdir.conf

# Real-time info on requests and configuration
Include conf/extra/httpd-info.conf

# Virtual hosts
Include conf/extra/httpd-vhosts.conf

# Local access to the Apache HTTP Server Manual
# Include conf/extra/httpd-manual.conf

# Distributed authoring and versioning (WebDAV)
Include conf/extra/httpd-dav.conf

# Various default settings
Include conf/extra/httpd-default.conf

# Secure (SSL/TLS) connections
Include conf/extra/httpd-ssl.conf
#
# Note: The following must must be present to support
# starting without SSL on platforms with no /dev/random equivalent
# but a statically compiled-in mod_ssl.
#
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin

</IfModule>


In reply to Juvenal Sahiri

Re: Elgg Block error after install

by Graeme Forrester -

I have ELGG 0.673 working happily with moodle 1.6, 1.6.1, 1.6.2 and now 1.7

I have only used the standard elgg .htaccess files without issue.

I found the greatest difficulty was in external RSS feeds in moodle which broke the ELGG link every time so I now only allow external RSS feeds in ELGG and not moodle which seems to work. This was due to the setting of proxy in moodle without the use of exceptions for local lan and I never solved it.

At this point I just leave proxy settings blank in moodle. 

This bit should fix your allow override for ELGG

<Directory />
Options FollowSymLinks
AllowOverride All
Order deny,allow
Deny from all
</Directory>

If not you may have to set up a separate entry for the ELGG directory.

Is ELGG working properly? ie can you login and find the files and weblogs links? Can you see your profile pictures?

In reply to Graeme Forrester

Re: Elgg Block error after install

by Juvenal Sahiri -
Graeme,
Thanks for getting back to me so quickly. I changed the htaccess file by inserting the allowoverride code you gave. When I then launch http://localhost/elgg, I get this error:
Elgg configuration error: .htaccess is missing. Please see INSTALL file.

Here is the content of the apache error log:
[Fri Jan 12 10:22:53 2007] [notice] Apache/2.2.3 (Win32) DAV/2 mod_ssl/2.2.3 OpenSSL/0.9.8d mod_autoindex_color PHP/5.2.0 configured -- resuming normal operations
[Fri Jan 12 10:22:53 2007] [notice] Server built: Sep 30 2006 21:24:06
[Fri Jan 12 10:22:53 2007] [notice] Parent: Created child process 1880
[Fri Jan 12 10:22:55 2007] [notice] Child 1880: Child process is running
[Fri Jan 12 10:22:55 2007] [notice] Child 1880: Acquired the start mutex.
[Fri Jan 12 10:22:55 2007] [notice] Child 1880: Starting 250 worker threads.
[Fri Jan 12 10:22:55 2007] [notice] Child 1880: Starting thread to listen on port 443.
[Fri Jan 12 10:22:55 2007] [notice] Child 1880: Starting thread to listen on port 80.

My question is: Since .htaccess is inside elgg directory, what is meant by install it?

Many thanks for your help
Juvenal
In reply to Juvenal Sahiri

Re: Elgg Block error after install

by Graeme Forrester -

Elgg ships with htaccess-dist which you rename .htaccess and leave it in the root of your ELGG subdirectory. Without it it doesn't work.

This code below is the .htaccess file - see the code in red that might be source of the problem but I have never had to change it as it always works out of the box.

<IfModule !mod_rewrite.c>
    # ugly ugly hack to detect missing mod_rewrite
    # RedirectMatch must be to an absolute destination, so forces 500 error...
    ErrorDocument 500 "Elgg error: Apache does not have mod_rewrite loaded. Please check your apache setup."
    RedirectMatch 302 .* index.php
</IfModule>

<Files "htaccess-dist">
    order allow,deny
    deny from all
</Files>

Options +FollowSymLinks

# PHP defaults to allowing file uploads of max 2MB, below is example option for 5MB.
# NB: Adjusting value may not work, depending on other configured php and apache limits
#php_value upload_max_filesize 5242880

# Not really necessary, just to be clean
#php_flag short_open_tag off
# Forgot that anyone might still have this turned on
#php_flag register_globals off

<IfModule mod_rewrite.c>

RewriteEngine on

# If Elgg is in a subdirectory on your site, you might need to add a RewriteBase line
# containing the path from your site root to elgg's root. e.g. If your site is
# http://example.com/ and Elgg is in http://example.com/sites/elgg/, you might need
#
#RewriteBase /sites/elgg/
#
# here, only without the # in front.
#
# If you're not running Elgg in a subdirectory on your site, but still getting lots
# of 404 errors beyond the front page, you could instead try:
#
#RewriteBase /

RewriteRule ^([0-9\-]+)\.css$ _templates/css.php?template=$1

RewriteRule ^(.+)\/rssstyles.xsl$ _rss/styles.php?rssurl=$1&url=$1

RewriteRule ^([A-Za-z0-9]+)\/dashboard(\/)?$ mod/adash/index.php?user=$1

RewriteRule ^([A-Za-z0-9]+)(\/)?$ profile/index.php?profile_name=$1
RewriteRule ^([A-Za-z0-9]+)\/profile(\/)?$ profile/index.php?profile_name=$1
RewriteRule ^([A-Za-z0-9]+)\/tags(\/)?$ search/personaltags.php?profile_name=$1
RewriteRule ^(([A-Za-z0-9])[A-Za-z0-9]+)\/rss\/?$ _rss/static.php?username=$1&userref=$2&type=profile
RewriteRule ^([A-Za-z0-9]+)\/rss\/(.+)\/?$ profile/rss2.php?profile_name=$1&tag=$2

RewriteRule ^([A-Za-z0-9]+)\/newsclient\/?$ _rss/subscriptions.php?profile_name=$1
RewriteRule ^([A-Za-z0-9]+)\/newsclient\/all\/?$ _rss/index.php?profile_name=$1
RewriteRule ^([A-Za-z0-9]+)\/newsclient\/all\/skip=([0-9]+)$ _rss/index.php?profile_name=$1&feed_offset=$2

RewriteRule ^([A-Za-z0-9]+)\/feeds\/?$ _rss/subscriptions.php?profile_name=$1
RewriteRule ^([A-Za-z0-9]+)\/feeds\/all\/?$ _rss/index.php?profile_name=$1
RewriteRule ^([A-Za-z0-9]+)\/feeds\/all\/skip=([0-9]+)$ _rss/index.php?profile_name=$1&feed_offset=$2

RewriteRule ^([A-Za-z0-9]+)\/weblog\/?$ _weblog/index.php?weblog_name=$1
ReWriteRule ^([A-Za-z0-9]+)\/weblog\/skip=([0-9]+)$ _weblog/index.php?weblog_name=$1&weblog_offset=$2
RewriteRule ^([A-Za-z0-9]+)\/weblog\/category\/([^\/]+)\/?$ _weblog/index.php?weblog_name=$1&filter=$2
ReWriteRule ^([A-Za-z0-9]+)\/weblog\/category\/([^\/]+)\/skip=([0-9]+)$ _weblog/index.php?weblog_name=$1&filter=$2&weblog_offset=$3
RewriteRule ^([A-Za-z0-9]+)\/weblog\/archive\/?$ _weblog/archive.php?weblog_name=$1
RewriteRule ^([A-Za-z0-9]+)\/weblog\/archive\/([0-9]+)\/([0-9]+)\/?$ _weblog/archive_month.php?weblog_name=$1&year=$2&month=$3
RewriteRule ^([A-Za-z0-9]+)\/weblog\/friends\/?$ _weblog/friends.php?weblog_name=$1
ReWriteRule ^([A-Za-z0-9]+)\/weblog\/friends\/skip=([0-9]+)$ _weblog/friends.php?weblog_name=$1&weblog_offset=$2
RewriteRule ^([A-Za-z0-9]+)\/weblog\/interesting\/?$ _weblog/interesting.php?weblog_name=$1
ReWriteRule ^([A-Za-z0-9]+)\/weblog\/interesting\/skip=([0-9]+)$ _weblog/interesting.php?weblog_name=$1&weblog_offset=$2
RewriteRule ^(([A-Za-z0-9])[A-Za-z0-9]+)\/weblog\/rss\/?$ _rss/static.php?username=$1&userref=$2&type=weblog
RewriteRule ^([A-Za-z0-9]+)\/weblog\/rss\/(.+)\/?$ _weblog/rss2.php?weblog_name=$1&tag=$2&modifier=is
RewriteRule ^([A-Za-z0-9]+)\/weblog\/rssnot\/(.+)\/?$ _weblog/rss2.php?weblog_name=$1&tag=$2&modifier=not
RewriteRule ^[A-Za-z0-9]+\/weblog\/([0-9]+)\.html$ _weblog/view_post.php?post=$1

RewriteRule ^tag\/(.+)\/?$ search/all.php?tag=$1
RewriteRule ^rsstag\/(.+)\/?$ search/rss.php?tag=$1
RewriteRule ^tag\/(.+)/ecl\/?$ search/ecl.php?tag=$1

RewriteRule ^([A-Za-z0-9]+)\/friends\/?$ _friends/index.php?friends_name=$1
RewriteRule ^([A-Za-z0-9]+)\/foaf\/?$ _friends/foaf.php?friends_name=$1

RewriteRule ^([A-Za-z0-9]+)\/communities\/?$ _communities/index.php?friends_name=$1
RewriteRule ^community\/([0-9]+)\/?$ _communities/community.php?community_id=$1

RewriteRule ^([A-Za-z0-9]+)\/files\/?$ _files/index.php?files_name=$1
RewriteRule ^([A-Za-z0-9]+)\/files\/([0-9]+)\/?$ _files/index.php?files_name=$1&folder=$2
RewriteRule ^([A-Za-z0-9]+)\/files\/([0-9\-]+)\/([0-9]+)\/(.+)$ _files/download.php?files_name=$1&folder=$2&filename=$4&id=$3
RewriteRule ^(([A-Za-z0-9])[A-Za-z0-9]+)\/files\/rss\/?$ _rss/static.php?username=$1&userref=$2&type=files
RewriteRule ^([A-Za-z0-9]+)\/files\/rss\/(.+)\/?$ _files/rss2.php?files_name=$1&tag=$2

RewriteRule ^_icon\/user/([-0-9]+)$ _icons/icon.php?id=$1
RewriteRule ^_icon\/user/([-0-9]+)\/([A-Za-z])\/([0-9]+)$ _icons/icon.php?id=$1&constraint1=$2&size1=$3
RewriteRule ^_icon\/user/([-0-9]+)\/([A-Za-z])\/([0-9]+)\/([A-Za-z])\/([0-9]+)$ _icons/icon.php?id=$1&constraint1=$2&size1=$3&constraint2=$4&size2=$5
RewriteRule ^_icon\/file/([-0-9]+)$ _files/icon.php?id=$1

# Some blogging clients probe Wordpress or MoveableType endpoints,
# redirect them to the Elgg xml-rpc endpoint
#
RewriteRule xml-rpc.php _rpc/RPC2.php
RewriteRule mt/mt-xmlrpc.cgi _rpc/RPC2.php

</IfModule>

Does Elgg actually run with your original configuration? If Elgg doesn't work then your integration won't work either.

In reply to Graeme Forrester

Re: Elgg Block error after install

by Juvenal Sahiri -
Graeme,
Many thanks.
I followed Elgg installation instructions indeed and renamed .htaccess-dist and config-dist to .htaccess and config.php respectively. I changed nothing else except to add the code you sent me. Had made sure that Allowoverride was on also in http file.

The code in red is commented out and therefore should not matter. And it is in the original htaccess-dist.

I've combed the web for a possible explanation without success. Guess I will never know if elgg moodle plugin works if I cannot install elgg itself. I have installed mediawiki, gallery2 and moodle with the same xampplite package without the slightest problem. It could well be that Elgg does not work with the apache or php version bundled in xampplite 1.55 (windows version). The only thing I will try next is test with another package and see if I get better luck.

Do you have yours working on windows?
In reply to Graeme Forrester

Re: Elgg Block error after install

by Geoffrey Rowland -

Graeme (or Penny or... anyone?)

I'm intrigued to hear you have Elgg 0.673 working with Moodle.

I have managed to get Elgg 0.651 working more or less correctly with the Moodle-Elgg integration block in Moodle 1.62+. The 'Join Now' button allows setup of an Elgg account and the block subsequently allows direct login to Elgg as expected. The RSS feed from Elgg to the Moodle block sort of works - but it just seems to display recent comments to blogs made by the user, not blogs themselves - is this your experience? - or have I misunderstood something here?

I have also installed Elgg 0.673 and this works well as a standalone - however the Moodle-Elgg integration block now seems broken, the 'Join Now' just leads to a blank page - I have seeen lots of discussions with similar symptoms for older versions of Elgg, but none of the proposed solutions appear to precisely correspond to our situation  - nor work for us. Any ideas? We are currently using PHP 5.1.6 - but had the same symptoms with PHP 4.3.9.

As an aside, Elgg has a rather fun Visualisation plugin, based on the Java applet Prefuse, to be found in the SVN repository (not as easy to find as Moodle's Plugins  wink) . In Elgg 0.673, all you have to do is to drop the /visavis folder into the Elgg /mod folder. In Elgg 0.651, you also have to add the following code to Elggs's includes.php file.

   /***************************************************************************
    *    PLUGIN INITIALISATION
    ****************************************************************************/
 
    // XMLRPC
        @include($CFG->dirroot . "units/rpc/main.php");
 
        if ($allmods = get_list_of_plugins('mod') ) {
           foreach ($allmods as $mod) {
                $mod_init = $mod . '_init';
                if (function_exists($mod_init)) {
                    $mod_init();
                   }
           }
        }

Regards

Geoff

In reply to Penny Leach

Re: Elgg Block error after install

by Ruben Jansen -

Hi,

I tried the elgg block and finally it worked on our server, but only on the internal network! In the lms-host I used internal addresses (192.168...) and in Moodle block_eportfolio_baseurl I tried also the internal address and it worked, but this is the address moodle uses to make the link to elgg. From outside (internet) the internal link didn't work (of course), but when I fill in the external URL in block_eportfolio_baseurl, a course in Moodle where I put the portfolioblock reacts very(!) slow and it shows the "join me"-button over and over again.

So, block_eportfolio_baseurl with the internal address is ok, but with the outside URL the portfolio-block seems not to get contact with elgg.

I put moodle in /html/moodle on our server and elgg in /html/elgg. Does someone have an idea?

In reply to Wei Tang

This forum post has been removed

The content of this forum post has been removed and can no longer be accessed.
In reply to Deleted user

Re: Elgg Block error after install

by Paolo Oprandi -
On submitting the ELGG profile I get:

The requested URL /elgg/paolo was not found on this server

Then if I go back to Moodle and click "Join now", which I guess should say something else now I have supposedly joined, I get as you people.

But in any case, I hoped username and password would be passed across from Moodle rather than manually having to create a new account. Didn't you expect the same?

Paolo
In reply to Paolo Oprandi

This forum post has been removed

The content of this forum post has been removed and can no longer be accessed.
In reply to Deleted user

Re: Elgg Block error after install

by Paolo Oprandi -
maybe or maybe it isn't desirable. I can't imagine why on either account.

But did you get 'the requested URL /elgg/ { username } was not found on this server'? If not, does anyone know why I do?
In reply to Paolo Oprandi

Re: Elgg Block error after install

by Penny Leach -
maybe you don't have mod_rewrite enabled. elgg requires mod_rewrite.
In reply to Penny Leach

Re: Elgg Block error after install

by Wei Tang -
Hi Penny,
I've already trun on mod_rewrite for elgg directory in httpd.conf and make sure there was a LoadModule command for mod_rewrite.

The Elgg works well itself with Moodle.So, I think it is not the problem of mod_rewrite.

Thanks for you help!

Tang
In reply to Deleted user

Re: Elgg Block error after install

by Penny Leach -
the rationale is that users might already have elgg accounts and therefore they might want to bind their moodle account to an existing account.

the model allows for one elgg that accepts incoming users from a number of moodles.
In reply to Deleted user

Re: Elgg Block error after install

by Graeme Forrester -

This is a real issue if you have ldap because Moodle doesn't store passwords from MS AD.

Perhaps for LDAP users (which anyone can set up with Open LDAP) there could also be an LDAP plugin / authentication for ELGG.

In reply to Graeme Forrester

Re: Elgg Block error after install

by Penny Leach -
why is it an issue? there doesn't need to be any sort of password transferral. Once you set up your account in elgg, it gets bound to your moodle account so that when you log in to moodle and visit a page with the block on it, you're automatically authenticated in elgg without any need for passwords at all, it uses a different authentication system.
In reply to Penny Leach

Re: Elgg Block error after install

by Paolo Oprandi -
Hi Penny,

>the rationale is that users might already have elgg accounts and therefore they might
>want to bind their moodle account to an existing account.

Ah yes... that makes sense! Also I guess that ePortfolio's are for the student and not solely linked to our taught (moodle) courses.

>maybe you don't have mod_rewrite enabled. elgg requires mod_rewrite

I see it in Loaded Modules of php_info(), so I guess it is enabled...
In reply to Paolo Oprandi

Re: Elgg Block error after install

by Penny Leach -
having it loaded as a module doesn't mean it's enabled. You need to add something like this to your apache config


AllowOverride FileInfo


See this doco for more information: http://httpd.apache.org/docs/1.3/mod/mod_rewrite.html

Although, if you're trying to use elgg WITHOUT mod_rewrite enabled, you'll see a lot of problems, elgg relies on it _heavily_. Also, there would be a lot of noise in the error log.. or maybe it wouldn't work at all, with a 500 internal server error.

So I'm not sure that's it.
In reply to Penny Leach

Re: Elgg Block error after install

by Wei Tang -
Thanks Penny!

I'm using AllowOverride All in my httpd.conf.

But still got object id# error for Elgg Moodle Module.

Tang
In reply to Wei Tang

This forum post has been removed

The content of this forum post has been removed and can no longer be accessed.
In reply to Deleted user

Re: Elgg Block error after install

by Wei Tang -
Hi Dave,

There still was object Id error after I removed 'networkaddress' => '' from $CFG->lmshosts and from the eportfolio settings area.

Could you please tell me how to put PHP code into files to debug my problem?

Thanks!

Tang
In reply to Wei Tang

This forum post has been removed

The content of this forum post has been removed and can no longer be accessed.
In reply to Deleted user

Re: Elgg Block error after install

by Julie soule -
Hi, all,
I'm testing the elgg integration block from my local elgg and moodle installations. I'm also getting this message: "Object id #15" when I click the join button from the Eportfolio block. I've tried Dave's suggestion but get no error.txt file. Has anyone found a solution to this problem?

Here are my Eportfolio block settings:
block_eportfolio_server:localelgg
block_eportfolio_token:asdf1234
block_eportfolio_networkaddress: (blank)
block_eportfolio_installid:localelgg
block_eportfolio_baseurl:http://localelgg

Here are my Elgg settings:
 $CFG->lmshosts = array('localelgg' => array('token' => 'asdf1234', 'confirmurl' => 'http://moodle/blocks/eportfolio/confirm.php ', 'baseurl' => 'http://moodle', 'name' => 'Your local Moodle'));

The steps I followed:
1. Logged into moodle as admin, added an eportfolio block to a course.
2. Clicked join now button.
3. Logged into Elgg with the news account (the admin account for elgg)
4. Returned to moodle, had to login again as admin
5. Returned to the course, still saw the "join now" button. clicked it.
6. Received this message: Object id #15

Thanks for any help!!
Julie
In reply to Deleted user

Re: Elgg Block error after install

by Bhupinder Singh -

Hi Dave,

I am having an issue which has baffelled me.

It is posted here:

http://moodle.org/mod/forum/discuss.php?d=47184#216971

Could you give your suggestions / guidance.

:\POST REPRODUCED:

 

I have installed the Elgg and Moodle and completed the integration.

After much trouble i was able to debug and login to elgg from moodle by going through the Eportfolio block was able to log into elgg. smile

The second time when I tried through a different user what was returned is a blank screen with the word OBJECT and nothing else. thoughtful

Pressing the Join button on the Eportfolio the screens that were referred to and in the sequence are as under:

First:

http://localhost/LMS/blocks/eportfolio/signupredirect.php

Second:

http://localhost/elgg/lms/join.php

RESULT :

Return on screen  =    OBJECT.

This is happening again and again.

I am stuck now and do not know how to proceed further. Look forward for your help and that of other moodlers to get out of this trouble spot. sad

Garry

In reply to Deleted user

This forum post has been removed

The content of this forum post has been removed and can no longer be accessed.
In reply to Deleted user

Re: Elgg Block error after install

by Bhupinder Singh -

Hello Dave,

 

I have installed as directed. There is no output file (result.txt) in the Elgg folder.

I am using windows. My path of thwe elgg is as under

e:Program files/easyphp/www/elgg

My moodle path is as under:

e:Program files/easyphp/www/Lms

The sequeine of events is that I am directed to the redirectpage and then to the join page.

The utput on the screen on the join page is (on the top lt hand corner:

OBJECT

There is no result.txt file generated.

Any futher suggestions.

Garry

 

In reply to Bhupinder Singh

Re: Elgg Block error after install

by Bhupinder Singh -

Dave,

This is incontinuation of my mail regarding use of the script suggested by you. I get an error file at my E:  named Elggdataerror.

 

This gives the following error

" Invalid IP address"

I am running a local machine where the installation is on widdows and using localhost.

Could you suggest what I should do.

The elgg installation is working fine independently and  so is the moodle installation.

Garry

In reply to Bhupinder Singh

This forum post has been removed

The content of this forum post has been removed and can no longer be accessed.
In reply to Deleted user

Re: Elgg Block error after install

by Bhupinder Singh -

Hi Dave,

As suggested I have made the changes.

Still I get the out put in the file [through use of code as]  Invalid IP Address.

The first login was successful it is the secod login and subsequent that the " The display on the screen is " OBJECT". this happens when i press the Join Button.

The error in the output file is INVALID IP ADDRESS.

Look for your suggestions as to where I should try to look for issues for having a successful login.

Garry

 

In reply to Bhupinder Singh

This forum post has been removed

The content of this forum post has been removed and can no longer be accessed.
In reply to Deleted user

Re: Elgg Block error after install

by Bhupinder Singh -

Hi Dave,

I have placed the code. Thereafter I tried to join .

The output I get in the output file is as under:

INVALID IP ADDRESS

Now checking the details on the IP addresses they are as under:

On the LMS side which call the Elgg application.

block_eportfolio_baseurl=>'http://localhost/elgg'

ON the Elgg Cofig file: 'baseurl' => 'http://localhost/lms'

Could you look at this and suggest .

Thanks and regards

Garry

 

 

In reply to Penny Leach

Re: Elgg Block error after install

by Paolo Oprandi -
Thanks, Penny, I am returning to look at ELGG again now. Sorry for the delay. Changing AllowOverride from 'None' to 'All' worked.  I'll look for a more secure command later, but 'FileInfo' didn't seem to work.  I still have the problems mentioned other than this though, but I will have a look again at what Dave Cannon has to say.
In reply to Paolo Oprandi

Re: Elgg Block error after install

by Graeme Forrester -

Elgg integration was working fine until upgrade to 1.6.2 and ELGG 0.65

Now all of the errors above are occurring.

Have tried the script in rss.php and keep getting invalid ip address. I can log in once and that is it. Every time after the join button is always visible instead of the portfolio.

It is as if it authenticates once and never again.

I have tried no ip address, the internal ip address of the server but the invalid ip address keeps coming up.

Has anyone solved this because objectid #15 keeps coming up. Allow override is set to all.

In reply to Graeme Forrester

Re: Elgg Block error after install

by Graeme Forrester -

I think that I have solved my issue at least in the short term.

If I use proxy server elgg doesn't synchadn doesn't load. As soon as I clear the proxy settings it works.

This is OK for my elgg integration but RSS external feeds now don't work.

Any ideas for how to get them both to work?