All Site Activity

  • iionly commented on the blog Elgg 3.0.3 released
    There shouldn't be any risk of losing data when replacing the files in the Elgg install folder with the files of a newer Elgg version. If you haven't modified any core files yourself, the only files that contain site-specific data are...
  • iionly replied on the discussion topic Spam Anmeldungen
    Captchas sind leider nicht mehr ausreichend genug, um Spammer draussen zu halten. Sie können wahrscheinlich immer noch die Anzahl der durch Spambots erstellten Accounts reduzieren aber nicht mehr vollständig (und manchmal werden Accounts... view reply
  • iionly replied on the discussion topic tidypics_v2.3.6 Link Blank
    Ich vermute, mit der Farbe "brau" meinst Du die "blauen" Titel der Bilder. Die Farbe für diesen Text wird in mod/tidypics/views/default/photos/css.php durch das color Attribut bei der Klasse tidypics-heading... view reply
  • freeman added a new discussion topic Spam Anmeldungen in the group German Support Group
    Hallo zusammen, auf meine webseite melden sich fast Täglich bts an trotz das ich das Plugin für Captcha installiert hab, gibt es um das zu stopen? Danke schonmal
    • Captchas sind leider nicht mehr ausreichend genug, um Spammer draussen zu halten. Sie können wahrscheinlich immer noch die Anzahl der durch Spambots erstellten Accounts reduzieren aber nicht mehr vollständig (und manchmal werden Accounts zum Spammen auch noch durch Personen erstellt, für die die Captchas dann noch weniger ein Hindernis sind).

      Du solltest auf jeden Fall das Spam Login Filter-Plugin verwenden (https://elgg.org/plugins/774755 bzw. Version 2.1.1 von https://github.com/beck24/spam_login_filter/releases/tag/2.1.1). Damit wird bei der Account-Registrierung anhand der eingeben Accountdaten (Benutzername und Email-Adresse) plus der IP-Adresse in der Datenbank von StopForumSpam.com geprüft, ob mit diesen Daten schon Accounts angelegt worden sind, die dann zum Spammen verwendet wurden. Damit Du auch selbst Spammer melden kannst, mußt Du Dich bei StopForumSpam.com registrieren und einen API-Key erzeugen. Diesen API-Key müßtest Du dann in den Plugin-Einstellungen des Spam Login Filter-Plugins eingeben. Dann hast Du die Möglichkeit, statt einen Accounts auf Deiner Seite einfach nur zu löschen diesen auch gleichzeitig als Spammer an StopForumSpam.com zu melden.

      Auch mit dem Spam Login Filter-Plugin wirst Du wahrscheinlich nicht 100%-ig verhindern können, dass sich Spammer registrieren. Aber hoffentlich reduziert sich die Anzahl. Und wenn Du die Spammer auf Deiner Seite beim Löschen der Accounts meldest, können sie sich mit den gleichen Anmeldedaten (und IP-Adresse) auch nicht wieder bei Dir oder einer anderen Seite einen Account anlegen. Je mehr Leute also die Spammer melden, desto besser für alle.

      Ich hab ein ähnliches Plugin wie das Spam Login Filter-Plugin geschrieben (http:blacklist https://elgg.org/plugins/1641554). Das funktioniert allerdings nicht ganz so erfolgreich, da man einerseits keine Spammer melden kann und die Datenbank, mit der die Accountdaten abgeglichen werden, hauptsächlich aus anderen Quellen stammt (also nicht in erster Linie Foren und andere Social Network-Seiten sondern eher von Email-Spammern). Im Prinzip kann man http:blacklist und Spam Login Filter beide parallel betreiben. Aber fürs erste würde ich raten, Spam Login Filter auf jeden Fall zu verwenden.

      Es gibt noch ein paar andere Plugin, die bei der Bekämpfung von Spam helfen sollten. Die setzten allerdings nicht bei der Accountregistrierung an sondern versuchen, Spammer zu identifieren, wenn sie was posten (mehrere Einträge in sehr kurzer Zeit) bzw. erlauben anderen Usern, Spam-Postings zu melden. Siehe https://elgg.org/plugins/821368, https://elgg.org/plugins/1508060 und https://elgg.org/plugins/1508071. Ich hab diese Plugins allerdings noch nicht selbst eingesetzt, da ich bisher noch kein gravierendes Spam-Problem hatte. Ich glaube aber, sie werden beispielsweise hier auf der Communits-Seite verwendet.

  • Jaqueline commented on the blog Elgg 3.0.3 released
    Yes, I would just replace the existing ones. I'm afraid of losing everything!
  • Jerome Bakker commented on the blog Elgg 3.0.3 released
    Hello, I'm with elgg 3.0.2, to upgrade to 3.0.3, is it possible to just send those to the server, replacing? Do you need to do something else? You could probaby overrule the files, but if files are (re)moved this will not take full...
  • Jaqueline commented on the blog Elgg 3.0.3 released
    Hello, I'm with elgg 3.0.2, to upgrade to 3.0.3, is it possible to just send those to the server, replacing? Do you need to do something else?
  • Jerome Bakker published a blog post Elgg 3.0.3 released
    A new update for Elgg 3.0 is ready
    • Hello, I'm with elgg 3.0.2, to upgrade to 3.0.3, is it possible to just send those to the server, replacing? Do you need to do something else?

      You could probaby overrule the files, but if files are (re)moved this will not take full effect.

      Have a look at http://learn.elgg.org/en/stable/admin/upgrading.html#b-manual-upgrade-legacy-approach

    • Yes, I would just replace the existing ones. I'm afraid of losing everything!

    • There shouldn't be any risk of losing data when replacing the files in the Elgg install folder with the files of a newer Elgg version. If you haven't modified any core files yourself, the only files that contain site-specific data are elgg-config/settings.php and maybe .htaccess (if you made any changes in this file). Additionally, the mod folder might contain 3rd party plugins you've added.

      A newer Elgg version might not only contain modified files and new files but there could also be some files no longer included in the new version. When overwriting the install folder with the new Elgg version you would replace the modified files and also add any new files. But the files no longer included in the new version would remain on your server (as they would not be touched by overwriting). Such obsolete files could (not necessarily do in any case) cause issues if not removed.

      Now you wouldn't have to search for any of the files that might need to be removed. My approach is as follows: I prepare a separate folder with the new Elgg version outside of the public_html folder (aka document root folder) on the server (you could also do this locally on your computer and upload once ready) where I not only add the Elgg core files of the new Elgg version but also add the folders of the 3rd party plugins used on the site in the mod directory. Then I check if there are any changes in elgg-config/settings.php and .htaccess I would have to merge. If not, I can just add these two files currently used on my site also to the separate folder.

      When you work with such a separate folder containing everything that is later to be placed into the target folder of your Elgg installation you can prepare the upgrade without any time pressure. And once you are ready the actual upgrade goes faster.

      When I'm ready I do a backup of current install folder (to be on the safe side in case anything unexpected happens) AND also backups of database and data directory (as the data that really makes the site are either in database or data directory).

      Once I have backups of everything the upgrade can start. It might be best to enable the maintenance mode now (keeping other users out reduces the risk of database changes at just the wrong time) and then also disable the caching options in the advanced site settings. Now you can simple delete the content of the install folder to be sure that no obsolute files remain. Then you can MOVE the content of the folder containing the new Elgg version and everything else into the Elgg install folder (moving goes much faster than copying). Once the install folder contains all files and folders of the new Elgg version plus the 3rd party plugins again you can run the upgrade scripts (either clicking on the Upgrade button in the admin dashboard or running site.url/upgrade.php in the browser - the latter methods might not work on Elgg 3 anymore if accessing this url is protected by the Elgg site setting). Once the upgrade script has finished (best to check in the admin area also if any async upgrades need to be run) you can enable the caching options again and then disable the maintenance mode. All in all the actual upgrade only takes a few minutes this way (time to prepare the separate folder with the new version not included), so downtime is minimal and you don't need to put yourself under any pressure to finish fast. And with backups of everything at hand you could restore the site as it was before the upgrade in case anything bad happens.

  • freeman replied on the discussion topic tidypics_v2.3.6 Link Blank
    super ich danke dir .... eine frage habe ich noch das sollte dann die letzte sein hoffe ich :) und zwar wie bekomme ich die schrieft wo brau ist geändert ? ( siehe bild ) hab alle css nachgeschaut aber nichts gefunden view reply
  • MyHoTFB.COM ® replied on the discussion topic Unable to make Memcache work on PHP 7.0
    I have had tried in past declaring singly array, but it didn't produce any result nor did it with exact as per your above declaration. As far as the server is concerned, Memcache is correctly installed in VPS server for 7.0 including... view reply
  • MyHoTFB.COM ® replied on the discussion topic Unable to make Memcache work on PHP 7.0
    I have had tried in past declaring singly array, but it didn't produce any result nor did it with exact as per your above declaration. As far as the server is concerned, Memcache is correctly installed in VPS server for 7.0 including... view reply
  • iionly replied on the discussion topic Please help Problem updating from 2.3.4 to 3.0.0
    Have you upgraded Elgg before or have you never tried it? Have you installed Elgg with composer or had you installed it by using the zip archive available here on the site? composer only deals with upgrading the content of the install folder... view reply
  • iionly replied on the discussion topic What the best Elgg 2.3 or Elgg 3
    The default theme of Elgg 3 has been quite thoroughly rewritten. It should cope better on varying screen resolutions (even if the de-facto default theme of Elgg 2, i.e. the Aalborg theme, was also a responsive theme). It should also be easier to... view reply
  • Abdulaziz replied on the discussion topic Please help Problem updating from 2.3.4 to 3.0.0
    It seems that this method does not work for Do you use the other manual way is by scanning the site files and add files of the new version, but this way will enable me to maintain the posts and evidence on the site? view reply
  • iionly replied on the discussion topic tidypics_v2.3.6 Link Blank
    Sorry. Ich hatte nicht gründlich genug nachgeschaut, was man alles anpassen muss, um die Anzahl der Bilder überall zu ändern. Für die Album-Ansichten müßtest Du in der Datei... view reply
  • iionly replied on the discussion topic Please help Problem updating from 2.3.4 to 3.0.0
    Problem with using elgg-cli is that the shell user you are logged in as might not have the necessary permissions to read/write the files and folders (e.g. data directory of Elgg) that would have to be accessed during the upgrade. To be honest, I... view reply
  • iionly commented on the plugin Profile Manager
    Which version of the Profile Manager plugin are you trying to use and which version of Elgg have you installed? You are posting your question on the page of Profile Manager version 10.0-beta which is rather outdated. If you are using version 2.3 of...
  • Without further info we can't say for sure. Though I rather think it's an install attempt on webhosting. view reply
  • RvR replied on the discussion topic Unable to make Memcache work on PHP 7.0
    You need PHP extension php-memcached and memcached server only. In Elgg settings.php use: $CONFIG->memcache = true; $CONFIG->memcache_servers = array ( array('localhost', 11211), ); // Namespace prefix... view reply
  • MyHoTFB.COM ® replied on the discussion topic Unable to make Memcache work on PHP 7.0
    does it mean memcached interexchanged with memcache ? otherwise speaking are you trying to say that memcached=memcache ? I think what are u r saying is memcached can not be quantified  memcache  as they... view reply