Thank U to everybody who work on this release!  Is there plan introduce again twitter search display widget on Elgg 1.8.x? Thank U.

Twitter has created new display requirements. That is issue #1. The have also turned off unauthenticated access to tweets. That is issue #2. There are two ways to get tweets:

1. Use the API (with authentication) to grab tweets and then build a display that satisfies Twitter's display requirements. The authentication part requires each user to authorize your Elgg site by going to Twitter.
2. Go to Twitter and create a widget and then embed that widget on your Elgg site per user.

Neither of those options provides the ease of use of the old widget and no one on the core team is working on a solution for either 1 or 2. If someone else wanted to implement this, we would certainly take a look at adding it back to Elgg.

@Den I've gotted 'Latest tweets' w/o creating widget on twitter.com. Just used abraham_twitteroauth.

'Search tweets' have some problems with it.

Here are 'widgets solutions' also:

http://community.elgg.org/plugins/1182711/2.0/twitter-widgets-pack

https://github.com/ColdTrick/widget_manager/commit/e36ac3c419388c7b05f4d1672115b45e27a1ead1

Thank U all, Thank U @RvR

Fatal error after upgrading from 1.8.15 to 1.8.16.

Creating a new photo album in tidypics gives no errors, but I'm unable to upload any photos.

Existing albums work fine.

From Apache's error log:

[Sun Jun 30 17:44:48 2013] [error] [client xxx.xxx.xxx.xxx] PHP WARNING: 2013-06-30 17:44:48 (CEST): "mkdir(): Permission denied" in file /home/domain/www/mod/tidypics/classes/TidypicsAlbum.php (line 48), referer: http://domain.com/photos/add/35

Access rights haven't changed on my Elgg data directory, but for some reason Elgg/TidyPics is no longer able to create directories.

If I manually create the directory it wants, upload goes well.

@slyhne: this already failed to work in Elgg 1.8.15. Either download Tidypics from github (https://github.com/cash/Tidypics/commits/master) or use my fork (http://community.elgg.org/plugins/1194049/1.8.1beta9/elgg-18-tidypics). In both versions the issue has been fixed.

@iionly

I did this in my test environment, but apparently failed to catch this error in 1.8.15.

Thank you very much

what is the seRver requirements for v1.8.16?I noticed the following error report when the site home page is being accessed :

"Fatal Error.

An unrecoverable error has occurred and has been logged. Contact the site administrator with the following information:

Exception #1380454030."

@kxx4: check your server log for the reason the fatal error occurs. There's no principle change of requirements between Elgg 1.8.16 and former versions of Elgg. But there might be an issue with a 3rd party plugin that causes an error on Elgg 1.8.16, so this plugin might require to be updated. But without any more details about the reasons for the fatal error there's no specific advice possible.

@iionly:how do I locate the path to the file which has all the settings, for example, the database name, the database username on elgg?

@kxx4 See on engine\settings.example.php and INSTALL.txt

The settings file is not where the errors are logged. You would have to look in the error log file (php error log and/or Apache error log). If you don't know where these files are on your server then ask your hoster as they should be able to tell you where to find the error logs.

@kxx4 If you asked about

the path to the file which has all the settings

then see on engine\settings.php

If you need your errors log then @iionly answered already

By default, for Apache web server is:

var/logs/apache2/error.log

I have accessed my error log on server and the following are reports. I need interpretation and advice,plz:

[Sun Sep 29 03:12:14 2013] [error] [client 192.187.96.94] Exception #1380449534: exception 'DatabaseException' with message 'Table './myserver_mysite/elgg_entities' is marked as crashed and should be repaired

[Sun Sep 29 03:12:14 2013] [error] [client 192.187.96.94] \t\t) and enabled='yes')' in /home/myserver/public_html/engine/lib/database.php:274

[Sun Sep 29 03:12:14 2013] [error] [client 192.187.96.94] #0 /home/myserver/public_html/engine/lib/database.php(416): execute_query('SELECT * from e...', Resource id #54)

[Sun Sep 29 03:12:14 2013] [error] [client 192.187.96.94] #1 /home/myserver/public_html/engine/lib/database.php(379): elgg_query_runner('SELECT * from e...', '', true)

[Sun Sep 29 03:12:14 2013] [error] [client 192.187.96.94] #2 /home/myserver/public_html/engine/lib/entities.php(664): get_data_row('SELECT * from e...')

[Sun Sep 29 03:12:14 2013] [error] [client 192.187.96.94] #3 /home/myserver/public_html/engine/lib/entities.php(787): get_entity_as_row(1)

[Sun Sep 29 03:12:14 2013] [error] [client 192.187.96.94] #4 /home/myserver/public_html/engine/lib/configuration.php(556): get_entity(1)

[Sun Sep 29 03:12:14 2013] [error] [client 192.187.96.94] #5 /home/myserver/public_html/engine/lib/elgglib.php(2164): _elgg_load_site_config()

[Sun Sep 29 03:12:14 2013] [error] [client 192.187.96.94] #7 /home/myserver/public_html/engine/lib/elgglib.php(784): call_user_func_array('_elgg_engine_bo...', Array)

[Sun Sep 29 03:12:14 2013] [error] [client 192.187.96.94] #8 /home/myserver/public_html/engine/start.php(99): elgg_trigger_event('boot', 'system')

[Sun Sep 29 03:12:14 2013] [error] [client 192.187.96.94] #9 /home/myserver/public_html/index.php(12): require_once('/home/myserver/...')

@ some point , the error report was :

[Sun Sep 29 21:28:49 2013] [error] [client 198.27.69.31] Exception #1380515329: exception 'DatabaseException' with message 'Table './myserver_mysite/elgg_entities' is marked as crashed and should be repaired, referer: http://mysite.com/

[Sun Sep 29 21:28:49 2013] [error] [client 198.27.69.31] \t\t) and enabled='yes')' in /home/myserver/public_html/engine/lib/database.php:274, referer: http://mysite.com/

[Sun Sep 29 21:28:49 2013] [error] [client 198.27.69.31] #0 /home/myserver/public_html/engine/lib/database.php(416): execute_query('SELECT * from e...', Resource id #54), referer: http://mysite.com/

[Sun Sep 29 21:28:49 2013] [error] [client 198.27.69.31] #1 /home/myserver/public_html/engine/lib/database.php(379): elgg_query_runner('SELECT * from e...', '', true), referer: http://mysite.com/

[Sun Sep 29 21:28:49 2013] [error] [client 198.27.69.31] #2 /home/myserver/public_html/engine/lib/entities.php(664): get_data_row('SELECT * from e...'), referer: http://mysite.com/

[Sun Sep 29 21:28:49 2013] [error] [client 198.27.69.31] #3 /home/myserver/public_html/engine/lib/entities.php(787): get_entity_as_row(1), referer: http://mysite.com/

[Sun Sep 29 21:28:49 2013] [error] [client 198.27.69.31] #4 /home/myserver/public_html/engine/lib/configuration.php(556): get_entity(1), referer: http://mysite.com/

[Sun Sep 29 21:28:49 2013] [error] [client 198.27.69.31] #5 /home/myserver/public_html/engine/lib/elgglib.php(2164): _elgg_load_site_config(), referer: http://mysite.com/

[Sun Sep 29 21:28:49 2013] [error] [client 198.27.69.31] #7 /home/myserver/public_html/engine/lib/elgglib.php(784): call_user_func_array('_elgg_engine_bo...', Array), referer: http://mysite.com/

[Sun Sep 29 21:28:49 2013] [error] [client 198.27.69.31] #8 /home/myserver/public_html/engine/start.php(99): elgg_trigger_event('boot', 'system'), referer: http://mysite.com/

[Sun Sep 29 21:28:49 2013] [error] [client 198.27.69.31] #9 /home/myserver/public_html/index.php(12): require_once('/home/myserver/...'), referer: http://mysite.com/

"Table './myserver_mysite/elgg_entities' is marked as crashed and should be repaired"

You would need to repair the entities table of your database. This should be possible for example via phpMyAdmin or whatever tool is available on your webspace administration frontend. If in doubt, ask your hoster support.

@iionly:Thanks.Would the repair be like restoring the database (I have a backup of the 1.8.8 just before upgrading to 1.8.16) or can I copy the elgg_entities table from my test site (running 1.8.16 )on localhost? Or what other steps should be taken to redeem this situation? advice accordingly. 

Repair means "repair" not "restore". If you have a recent backup available that is recent enough for your liking you can also restore the database using it. The alternative is trying to repair the corrupt table: http://php.about.com/od/mysqladministration/qt/repair_mysql.htm.

A database repair is initiated.It seemed to have crashed the table again.

The present error report is as follows :" Fatal error: Allowed memory size of 262144 bytes exhausted (tried to allocate 19456 bytes) in /home/myserver/public_html/engine/lib/elgglib.php on line 1358"
The memory issue seems to be a source code/script issue.my site database seems to have a memory of abt 400mb+.
Advice.

the part of the script in :

/home/myserver/public_html/engine/lib/elgglib.php on line 1358"  =   str_replace($quotes, $encoded, $_SERVER['REQUEST_URI']);

/home/belzlon0/public_html/engine/lib/elgglib.php on line 1281 = $stack[] = "[#$i] {$trace['file']}:{$trace['line']}";

Advice

Allowed memory size of 262144 bytes exhausted

Is 262144 really the number that's in the error message? This is awefully low! It's only 256 kByte of allowed memory. This is not depending on the memory of your server but rather what's set for the php variable memory_limit. By default the memory limit for processing scripts is set to 64M in Elgg's .htaccess. Check what's set there. You can also use php_info() to get the info about what limit is actually in use (as the memory limit is maybe restricted to 256 kByte in the server's php.ini). If you can't modify php.ini you would need to contact your hoster - maybe they restricted the memory limit. In any case, 256 kByte is MUCH to low!

@ iionly:How can I gain access to the elgg script in my server to diable the plugins?my host has adjusted the memory limit to 1024mb and it didn't resolve the issue.

@ Kxx4, One of your problems "memory limits and PHP.INI issue" can be solved farst by reading this discussion

http://community.elgg.org/discussion/view/1511787/can-anyone-suggest-a-video-player-for-elgg-with-no-bugs

Hope your memory issue can be solved...

Thanks.

@ tom: thanks but the memory limit has been increased and yet it didn't resolve the issue. I need to know how to disable the plugins,without going through the front page, as this issue seems to be from the elgg script or plugins. The site is not loading.

Create a file that you name "disabled" in the mod directory of your site. The file can be empty (content is not relevant) but the name must be "disabled". If this file is present all your plugins will be made inactive and you should be able to access your site. There you can disable any plugin for real, i.e. it will stay disabled when you remove the "disabled" file again.

Does the error message still says "262144" bytes? If yes, this limit must be set somewhere else where your hoster has not changed it, for example in Elgg's .htaccess.