Look at this code.

Perhaps, you want to learn docs.

it didnot work for me  can you try it ? it is very confusing i found this code :-

if you draw a 'widget' layout (like done in https://github.com/Elgg/Elgg/blob/a836dda6e17954f8825c728d69b6113e38a01332/mod/dashboard/views/default/resources/dashboard.php#L5-L11) the function 'elgg_can_edit_widget_layout()' is called which triggers a hook to allow users to add widgets when the function returns TRUE.

See https://github.com/Elgg/Elgg/blob/a836dda6e17954f8825c728d69b6113e38a01332/engine/lib/widgets.php#L39-L52

Only this...

I can’t help you anymore because I don’t use CentOS (in fact, I don’t understand why people choose it).
I believe this is a common bug for all CentOS users.

If you don't find help here then refer to specialized sites with advanced CentOS users.

Robert,

When I installed Elgg 3.3.16 on the same system as yours, I did not have the site secret issue. But I encountered it later when trying to migrate Elgg 2.x data to Elgg3.x database.

I did not use 'vendor/elgg/elgg/elgg-cli' like you did when installing Elgg. I do not know if that is the cause of this issue or not. What I did was running 'vendor/bin/elgg-cli install' inside the project directory.

With that being said, below is how I debug this site secret issue. 

1. If you have an access to your MariaDB server, you can get the site secret from the config table - select value from {prefix}config where name like '%site_secret%';. 

2. If the query above returns a value, then copy it (only string inside the double quotes) and paste it to the elgg-config/settings.php - $CONFIG->__site_secret__ = 'paste your site secret here';

@Nikolai:

That thread is still revolving around permissions issues with the elgg directories. I've already checked all of that several times over.

I use CentOS because I'm familiar with the Red Hat ecosystem and use it for all of my projects. I've not had any major issues configuring a CentOS server to run anything to this extent before.

If this actually is a really common scenario, that apparently there's something about the CentOS environment that is consistently causing issues for people, would it be worth it at this point to file a bug on the Github issue tracker? I was originally thinking that my issues were rooted in dumb newbie mistakes that could be easily rectified, so I avoided posting my issue there. Now that I'm seeing that issues with CentOS are not particularly rare, I'm becoming more inclined to file an issue.

@seri_ng:

Thanks much for the hint about the config value in the settings file. I tried setting my own temporary dummy site secret in the hopes I could at least get Elgg to 'boot' properly and let me reset it automatically, but alas there is now a different error about an SQL query failure, which implies there's more deep-seated breakage in the database than I have much of a chance at fixing by hand being completely new to Elgg.

According to the tech guys at web-hosting company, the issue is due to is due to incompatible PDO signatures between the products core and PHP8. Any idea how to fix it and not happen it again? Thanks.

PHP Fatal error:  Declaration of Doctrine\DBAL\Driver\PDOConnection::query() must be compatible with PDO::query(string $query, ?int $fetchMode = null, mixed ...$fetchModeArgs) in /home/xxxx/xxxxdotcom/elgg3/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOConnection.php on line 81

Elgg 3.x isn't compatible with PHP 8.

You'll have to wait until Elgg 4 is released, that has support for PHP 8

@Jerome Bakker   is the master version at github equivalent to Elgg 4 OR unlike other Elgg releases is it possible to release an Elgg 4 beta as php 8 is new and there will be many wrinkles to smooth out in the Elgg-php8x combination?

Does this also mean as php7.4 will be nearing EOL, all Elgg 2x and 3x versions will stop working or will be there be patches to make it work in php8x? Thanks.

I don't understand how the landing page for university differs from another website but you can try this plugin.

You can find more examples on Showcase page.

Or look at our social apps.

You can try a demo site even.

If you want a custom solution then welcome to this group.

You can't because Elgg is still under development.

But you can try it as is.

So, the "master" there is actually equivalent to elgg 4 beta? Thanks.

Simple experiment – Excellent results

Disclaimer: May upset Relational DB experts :)

In our case we have 13 filters, each is based on one metadata. For each filter we need 2 Joins (for the metadata and metastring tables) and Wheres with 2 sections (for the metadata name.id and the value). All together 26 Joins and 26 wheres., some of them are quite heavy like calculation the distance between two geographical point on the globe.

However, the page is very slow with 7 filters, and dead with 10 or more.

So, we did a simple experiment. We added a table to the Elgg database with foreign key e.guid and duplicated the relevant metadatas as columns in the new table. The query is composed of one Join (with elgg_entities) and 13 Wheres.

Now the page loads in about a second.

Of course, this is not the best practice but it may be a solution.

We would appreciate any reflection on this experiment.

Is it safe?

Are there other alternatives?

Do future versions of Elgg have solutions to such problem?

Thank you.

In Elgg 3 the normalization of the metadata/metastring table was removed. This will help in speeding up those kind of queries.

Time to update ;)

Thank you Jerome