How to reach GDPR compliance without Flarum 2 ?

talkie

Welcome community, I am brand new to Flarum! No installation, yet.
I see version 2 with GDPR compliance is on the way, but lots of extension are not ported yet, also some I would like to use in a new setup of a productive forum. Also installing version 2.0 seems not to be recommended now, right?
But I fear GDPR non-compliance would not be a good idea in a commercial forum.
Whats your way to get around this issue?
Kind regards 🙂

luceos

The gdpr extension works on v1.x too. Not sure it was published as flarum/gdpr yet, it might still be Blomstra/gdpr

talkie

luceos

Wow, that was a quick answer, thank you luceos!

When I understand it the right way, Blomstra extensions are the premium extensions, right?
The extensions filter says it's a flarum extension, not premium.

So even though the extension description states that gdpr is "Unlikely to work with Flarum v1.8.10."
and requirements are

flarum/core - v2.0 or higher
PHP - 8.2 or higher

you say it will work on v1.x too.

Ok, then I will give it a try out 🙂

flavour1

luceos

The gdpr extension works on v1.x too.

That would be great !
Could you please give some hints on how install flarum/gdpr (or Blomstra/gdpr) on Flarum 1.8.10 ?

composer require flarum/gdpr:^1.8.10

gives me

Your requirements could not be resolved to an installable set of packages.

Problem 1
- Root composer.json requires flarum/gdpr ^1.8.10, found flarum/gdpr[dev-main, dev-master, 0.1.0-beta.1, ..., 0.1.0-beta.20, 1.0.0-beta.1, 1.0.0-beta.2, 1.0.0-beta.3, v2.0.0-beta.1, v2.0.0-beta.2, v2.0.0-beta.3, 2.x-dev] but it does not match the constraint.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

Flarum core: 1.8.10 PHP version: 8.3.20-nmm1 MySQL version: 10.11.13-MariaDB-0ubuntu0.24.04.1-log Loaded extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, pcntl, random, Reflection, SPL, session, standard, sodium, mysqlnd, PDO, xml, bcmath, bz2, calendar, ctype, curl, dba, dom, mbstring, fileinfo, ftp, gd, gettext, gmp, iconv, imagick, imap, intl, ldap, mailparse, exif, mysqli, odbc, pdo_dblib, PDO_Firebird, pdo_mysql, PDO_ODBC, pdo_pgsql, pdo_sqlite, pgsql, Phar, posix, pspell, readline, redis, shmop, SimpleXML, soap, SourceGuardian, sqlite3, sysvsem, sysvshm, tidy, tokenizer, xmlreader, xmlwriter, xsl, zip, ionCube Loader +-----------------------------------+---------+--------+ | Flarum Extensions | | | +-----------------------------------+---------+--------+ | ID | Version | Commit | +-----------------------------------+---------+--------+ | flarum-flags | v1.8.2 | | | flarum-approval | v1.8.2 | | | flarum-tags | v1.8.4 | | | flarum-suspend | v1.8.4 | | | fof-pages | 1.0.8 | | | flarum-sticky | v1.8.2 | | | fof-byobu | 1.4.2 | | | fof-sitemap | 2.2.1 | | | fof-discussion-language | 1.3.6 | | | flarum-lock | v1.8.2 | | | webbinaro-calendar | 1.7.0 | | | walsgit-external-links-in-new-tab | 1.1.2 | | | v17development-blog | v0.8.0 | | | ramon-colored | 1.1.1 | | | migratetoflarum-canonical | 1.0.0 | | | huseyinfiliz-notificationhub | v0.3 | | | glowingblue-password-strength | 4.0.0 | | | fof-user-directory | 1.4.0 | | | fof-user-bio | 1.4.2 | | | fof-upload | 1.8.3 | | | fof-terms | 1.4.2 | | | fof-subscribed | 1.1.4 | | | fof-profile-image-crop | 1.1.6 | | | fof-polls | 2.2.14 | | | fof-nightmode | 1.6.0 | | | fof-moderator-notes | 1.3.0 | | | fof-links | 1.3.0 | | | fof-linguist | 1.1.5 | | | fof-formatting | 1.1.0 | | | fof-drafts | 1.2.12 | | | fof-doorman | 1.1.5 | | | fof-discussion-thumbnail | 1.1.3 | | | fof-direct-links | 1.0.1 | | | flarum-subscriptions | v1.8.1 | | | flarum-statistics | v1.8.1 | | | flarum-mentions | v1.8.5 | | | flarum-markdown | v1.8.1 | | | flarum-likes | v1.8.1 | | | flarum-lang-german | 1.19.0 | | | flarum-lang-english | v1.8.0 | | | flarum-extension-manager | v1.0.7 | | | flarum-bbcode | v1.8.0 | | | datlechin-landing-page | 0.1.0 | | | datlechin-copy-links | v1.0.1 | | | askvortsov-pwa | v3.4.1 | | | acpl-mobile-tab | 1.4.5 | | +-----------------------------------+---------+--------+!<

luceos

Use composer require blomstra/gdpr:"*"

And no Blomstra extensions aren't all premium ones, only a handful are.

luceos

luceos composer require blomstra/gdpr:"@beta"

This should work.

flavour1

thank you @luceos for the quick reply!

unfortunately I still can not install it.

composer require blomstra/gdpr:"*" --verbose

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires blomstra/gdpr *, found blomstra/gdpr[dev-main, dev-master, 0.1.0-beta.1, 0.1.0-beta.2, 0.1.0-beta.3, 0.1.0-beta.4, 0.1.0-beta.5, 0.1.0-beta.6, 0.1.0-beta.7, 0.1.0-beta.8, 0.1.0-beta.9, 0.1.0-beta.10, 0.1.0-beta.11, 0.1.0-beta.12, 0.1.0-beta.13, 0.1.0-beta.14, 0.1.0-beta.15, 0.1.0-beta.16, 0.1.0-beta.17, 0.1.0-beta.18, 0.1.0-beta.19, 0.1.0-beta.20, 1.0.0-beta.1, 1.0.0-beta.2, 1.0.0-beta.3, v2.0.0-beta.1, v2.0.0-beta.2, v2.0.0-beta.3, 2.x-dev] but it does not match your minimum-stability.


Installation failed, reverting ./composer.json and ./composer.lock to their original content.

I also tried ">=1.0 <2.0"

Do you have any idea how to circumvent those version conflicts?
maybe composer update --stability=dev or some further dependencies can help to install blomstra/gdpr on 1.8.10?

flavour1

luceos
thank you very much!

It worked this way with flarum-gdpr 1.0.0-beta.3

During first testing, a data-export download resulted in an unknown error, but the download worked anyway.

Unhandled Promise Rejection: [object Object]
(anonymous function) (forum.js:2:262196)

   return app
      .request<ApiPayloadSingle>({
        method: this.exists ? 'PATCH' : 'POST',
        url: app.forum.attribute('apiUrl') + this.apiEndpoint(),
        body: request,
        ...options,
      })
      .then(
        // If everything went well, we'll make sure the store knows that this
        // model exists now (if it didn't already), and we'll push the data that
        // the API returned into the store.
        (payload) => {
          return this.store.pushPayload<this>(payload);
        },

        // If something went wrong, though... good thing we backed up our model's
        // old data! We'll revert to that and let others handle the error.
        (err: Error) => {
          this.pushData(oldData);
          m.redraw();
          throw err;
        }
      );
  }

anyway - thank you for your fast replies and happy weekend!

talkie

flavour1 It worked this way with flarum-gdpr 1.0.0-beta.3

@flavour1, do you have a typo here and meant "flarum-gdpr 2.0.0-beta.3" ?
Or did you get gdpr running on 1.8.10 ?

luceos

talkie no it really should be

composer require blomstra/gdpr:"@beta"

flavour1

talkie

no and yes ;-)
I installed on Flarum core: 1.8.10 with

composer require flarum/gdpr:"@beta"

which gave me the output

./composer.json has been updated
Running composer update flarum/gdpr
Loading composer repositories with package information
Updating dependencies
Lock file operations: 0 installs, 1 update, 0 removals
  - Upgrading flarum/gdpr (0.1.0-beta.20 => 1.0.0-beta.3)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 0 installs, 1 update, 0 removals
  - Downloading flarum/gdpr (1.0.0-beta.3)
  - Upgrading flarum/gdpr (0.1.0-beta.20 => 1.0.0-beta.3): Extracting archive

So the extension runs as 1.0.0-beta.3 on Flarum 1.8.10 and seems to work fine!

(except the mentioned error message in the browser when i trigger the download of exported user data from the notifications field. I have to investigate further, so far I assume its not an issue of the gdpr extension itself, but somehow related to ExtensionMessagingService. No big deal, but it would be interesting to know, if you get the same error message on your flarum installation)

talkie

flavour1

Ah, now I understand, I think.
1.0.0-beta.3 is the version of flarum/gdpr. I mistook it with the flarum version.
Thanks for the explanation, I have no experience with any install so far.