THis is how it's done in mod/market/views/default/river/object/market/create.php :

<?php
/**
* Market river view.
*/

$object = $vars['item']->getObjectEntity();
$excerpt = strip_tags($object->excerpt);
$excerpt = elgg_get_excerpt($excerpt);

$img = elgg_view('output/img', array(
    'src' => "market/image/{$object->guid}/medium/{$object->time_updated}",
    'class' => 'elgg-photo',
));
$image = elgg_view('output/url', array(
    'href' => "market/view/{$object->guid}/" . elgg_get_friendly_title($object->title),
    'text' => $img,
));

echo elgg_view('river/item', array(
    'item' => $vars['item'],
    'message' => $excerpt,
    'attachments' => $image,
));

Hi,

you followed all the instructions of http://docs.elgg.org/wiki/Duplicate_Installation?

Does the webserver have read rights on the new dataroot location and/or all the files?

• Have you checked the data folder and its permissions?
• Are you sure files all files are migrated completely?
• See this link also http://docs.elgg.org/wiki/No_images

The code that sends the validation email is in the file uservalidationbyemail/lib/functions.php. The line

$body = elgg_echo('email:validate:body', array($user->name, $site->name, $link, $site->name, $site->url));

creates the email body.

If you want to change the order of the arguments or don't want to use any of them you would to have modify the array entries accordingly.

Folders won't get erased when overwriting the files. Overwriting the existing Elgg version with a newer version will only replace the files included in Elgg core within these folders, i.e. any 3rd party plugins in mod or any additional files in _graphics or elsewhere will stay untouched. Also, the files engine/settings.php and .htaccess won't be replaced as they are not included in the Elgg zip archive. So, your site should continue to work after overwriting the files and running upgrade.php. If you want to be sure that no obsolete files/folders remain when upgrading your site you could erase the old version (only Elgg core) before copying the new version on the server. That's what I do normally: I erase all files in Elgg's root folder except .htaccess. I erase all folders except engine and mod. Then I erase everything within the engine folder exept settings.php and all bundled plugin folders in mod. Now I can copy the new version into the Elgg folder being sure that now obsolete files remain. Last thing to do is to check any possible updates necessary in settings.php (compared with settings.example.php) and .htaccess (compared with htaccess_dist), then running upgrade.php. Done! Of course, this will only work easily if you haven't made any changes in any Elgg core files you would need to re-edit into the same files in the new Elgg version.

If overwriting the files / directories fails for you, this might be caused by the tool you use for moving / copying the files. First, try to "copy" instead of "move" as it might only be a matter of file/directory access permissions. If this also fails to work you might need to use another tool for copying the files.

Hey. my site is multilingual also, every country is welcome. Would be very good to be able to have a geo script that detects their default language when the page is loaded automatically, but also a pull down menu to select language in the corner would be awesome with a small flag by the language.

I am hoping someone can create a plugin one day with all kinds of language packs included and a way for the end-user to be able to select a desired one from a menu, this would be super.

possible? yes
this topic is kinda several years old
i had coded some language funkyness
for purus' french learning elgg-site ~1 yr back
and then promptly lost all the code ;o(
no idea where that code hides @now but it did all
yr language detect stuff and all ther cwapzrz too!