Code for database forms and Drupal module for the Lobbywatch.ch project

Lobbywatch

Last update: Dec 1, 2022

Related tags

Starter Projects mysql python bash docker php drupal politics rest-api restapi drupal-module php-generator

Overview

Lobbywatch.ch

Lobbywatch.ch - the platform for transparent politics.

Lobbywatch.ch maintains a database with links of politicians and lobby groups.

This repository contains the

edit forms,
Drupal lobbywatch module for a textual representation,
DB structure, and
visualizations.

The data are not stored in this repository.

Requirements

PHP 7.2
PHP composer
MySQL 5.7.26
Drupal 7
bash 4.4
ImageMagick

More info, see https://lobbywatch.ch/de/seite/technik

Edit forms generation

The edit forms are built with the PHP Generator for MySQL Professional. Its a commercial tool (about 100$).

PHP Generator for MySQL Professional 18.3.0.2 (08.05.2018)

Setup

PHP

composer install

DB

mysql -u root

Remove NO_ZERO_IN_DATE,NO_ZERO_DATE, ONLY_FULL_GROUP_BY form sql_mode

show databases;

create database lobbywatch; create database lobbywatchtest;

./deploy.sh -l= -r -s prod_bak/bak/dbdump_struct_lobbywat_lobbywatch_20170714_143332.sql

GRANT SELECT ON . TO 'lw_reader'@'localhost' IDENTIFIED BY 'PASSWORD'; GRANT SELECT ON . TO 'lw_reader'@'127.0.0.1' IDENTIFIED BY 'PASSWORD';

FLUSH PRIVILEGES;

Edit forms

Build

./build.sh

Deploy

./deploy.sh -s -p

See parameters with

./deploy.sh -h

Drupal Theme

The Drupal 7 theme transparent_sky is in a separte git repository: https://github.com/Lobbywatch/transparent_sky

License

Source of Lobbywatch.ch is licensed under GPL, see LICENSE.

Comments

feat(DB): Neue Column freigabe_queue.tweet_de_id

Fügt der Tabelle freigabe_queue die neuen Spalten tweet_de_id und tweet_fr_id, in welchen die IDs der entsprechend ausgelösten Tweets hinterlegt werden.

Zusätzlich wurde der enum von status erweitert um in_triage und ignoriert.

opened by knutwannheden 3
data_interface examples do not work

I just tried out a couple of the examples mentioned here: https://github.com/lobbywatch/lobbywatch/blob/master/drupal/lobbywatch/lobbywatch_data/data_interface_description.md

E.g. Example 1 call http://lobbywatch.ch/de/data/interface/v1/json/table/branche/flat/id/1 yields a 404 Error.

opened by flurischt 3
fix(DB): Only insert into `freigabe_queue` on first "freigabe"

Nur bei der ersten Freigabe soll ein Eintrag in die Queue geschrieben werden. Interessenbindungen werden bei jeder Authorisierungsrunde neu freigegeben.

opened by knutwannheden 1
feat(DB): Neue freigabe_queue Tabelle

Neue generische freigabe_queue Tabelle, welche aktuell mit interessenbindung-Einträge befüllt wird, jedes Mal, wenn sich das freigabe_datum ändert.

Die Idee ist, dass die Einträge in dieser Queue bestehen bleiben, auch nachdem sie abgearbeitet wurden, damit dies bei Bedarf auch später nachvollzogen werden kann.

opened by knutwannheden 1
build(deps): bump phpmailer/phpmailer from 6.2.0 to 6.4.1
Bumps phpmailer/phpmailer from 6.2.0 to 6.4.1.

Release notes

Sourced from phpmailer/phpmailer's releases.

PHPMailer 6.4.1

This is a security release.

SECURITY Fixes CVE-2020-36326, a regression of CVE-2018-19296 object injection introduced in 6.1.8, see SECURITY.md for details

Reject more file paths that look like URLs, matching RFC3986 spec, blocking URLS using schemes such as ssh2

Ensure method signature consistency in doCallback calls

Ukrainian language update

Add composer scripts for checking coding standards and running tests

Thanks to Fariskhi Vidyan for the report and assistance, and Tidelift for support.

PHPMailer 6.4.0

This is a maintenance release. The changes introduced in 6.3.0 for setting an envelope sender automatically when using mail() caused problems, especially in WordPress, so this change has been reverted. It gets a minor version bump as it's a change in behaviour, but only back to what 6.2.0 did. See #2298 for more info.

Other changes:

Check for the mbstring extension before decoding addresss in parseAddress, so it won't fail if you don't have it installed

Add Serbian Latin translation (sr_latn)

Enrol PHPMailer in Tidelift, because supporting open-source is important!

PHPMailer 6.3.0

This is a maintenance release.

Handle early connection errors such as 421 during connection and EHLO states

Switch to Github Actions for CI

Generate debug output for mail(), sendmail, and qmail transports. Enable using the same mechanism as for SMTP: set SMTPDebug > 0

Make the mail() and sendmail transports set the envelope sender the same way as SMTP does, i.e. use whatever From is set to, only falling back to the sendmail_from php.ini setting if From is unset. This avoids errors from the mail() function if Sender is not set explicitly and php.ini is not configured. This is a minor functionality change, so bumps the minor version number.

Extend parseAddresses to decode encoded names, improve tests

Changelog

Sourced from phpmailer/phpmailer's changelog.

Version 6.4.1 (April 29th, 2021)

SECURITY Fixes CVE-2020-36326, a regression of CVE-2018-19296 object injection introduced in 6.1.8, see SECURITY.md for details

Reject more file paths that look like URLs, matching RFC3986 spec, blocking URLS using schemes such as ssh2

Ensure method signature consistency in doCallback calls

Ukrainian language update

Add composer scripts for checking coding standards and running tests

Version 6.4.0 (March 31st, 2021)

Revert change that made the mail() and sendmail transports set the envelope sender if one isn't explicitly provided, as it causes problems described in PHPMailer/PHPMailer#2298

Check for mbstring extension before decoding addresss in parseAddress

Add Serbian Latin translation (sr_latn)

Enrol PHPMailer in Tidelift

Version 6.3.0 (February 19th, 2021)

Handle early connection errors such as 421 during connection and EHLO states

Switch to Github Actions for CI

Generate debug output for mail(), sendmail, and qmail transports. Enable using the same mechanism as for SMTP: set SMTPDebug > 0

Make the mail() and sendmail transports set the envelope sender the same way as SMTP does, i.e. use whatever From is set to, only falling back to the sendmail_from php.ini setting if From is unset. This avoids errors from the mail() function if Sender is not set explicitly and php.ini is not configured. This is a minor functionality change, so bumps the minor version number.

Extend parseAddresses to decode encoded names, improve tests

Commits

9256f12 6.4.1

fd7ec67 Add more tests for bad paths

26f2848 Reorder path checks, fixes CVE-2020-36326

bc51d1f Add not-strictly-necessary backslash to avoid ambiguity

7f267fb Match all RFC3986 scheme patterns

b1038ee Add composer scripts for syntax check and tests

0acc57d make text compliance with Ukrainian orthography (#2317)

08cf13b Make use of $to in doCallback consistent, see #2305

be427db Make use of $to in doCallback consistent

050d430 6.4.0

Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR

@dependabot recreate will recreate this PR, overwriting any edits that have been made to it

@dependabot merge will merge this PR after your CI passes on it

@dependabot squash and merge will squash and merge this PR after your CI passes on it

@dependabot cancel merge will cancel a previously requested merge and block automerging

@dependabot reopen will reopen this PR if it is closed

@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot use these labels will set the current labels as the default for future PRs for this repo and language

@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language

@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language

@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

dependencies
opened by dependabot[bot] 1
Indicate if no compensation data available

Sent: Thursday, June 1, 2017 8:44 AM Subject: Re: Einkommen Parlamentarier

Guten Morgen allerseits

Die Reaktion von XX ist nicht überraschend, ich habe selber einige ähnliche Reaktionen gehört. Dort, wo keine Angaben vorhanden sind (und das ist bekanntlich in den meisten Fällen der Fall), wirkt unsere Ansage bezüglich deklarierten Einkommen wie ein falsches Versprechen oder wie ein technischer Fehler.

Ich schlage deshalb vor, dass dort, wo wir über keinen Wert verfügen, defaultmässig „Keine Angabe“ oder „Keine Angabe bekanntgegeben“ (oder so ähnlich) anzeigen (müsste dann natürlich noch übersetzt werden). Dann ist’s für alle klar.

We should write: Entschädigung Keine Angabe

opened by scito 1
build(deps): bump phpmailer/phpmailer from 6.2.0 to 6.5.0
Bumps phpmailer/phpmailer from 6.2.0 to 6.5.0.

Release notes

Sourced from phpmailer/phpmailer's releases.

PHPMailer 6.5.0

This is a security release.

SECURITY Fixes CVE-2021-34551, a complex RCE affecting Windows hosts. See https://github.com/PHPMailer/PHPMailer/blob/HEAD/SECURITY.md for details.

The fix for this issue changes the way that language files are loaded. While they remain in the same PHP-like format, they are processed as plain text, and any code in them will not be run, including operations such as concatenation using the . operator.

Deprecation The current translation file format using PHP arrays is now deprecated; the next major version will introduce a new format.

SECURITY Fixes CVE-2021-3603 that may permit untrusted code to be run from an address validator. See https://github.com/PHPMailer/PHPMailer/blob/HEAD/SECURITY.md for details.

The fix for this issue includes a minor BC break: callables injected into validateAddress, or indirectly through the $validator class property, may no longer be simple strings. If you want to inject your own validator, provide a closure instead of a function name.

Haraka message ID strings are now recognised

Thanks to Vikrant Singh Chauhan, listensec.com, and the WordPress security team for reporting and assistance with this release.

PHPMailer 6.4.1

This is a security release.

SECURITY Fixes CVE-2020-36326, a regression of CVE-2018-19296 object injection introduced in 6.1.8, see SECURITY.md for details

Reject more file paths that look like URLs, matching RFC3986 spec, blocking URLS using schemes such as ssh2

Ensure method signature consistency in doCallback calls

Ukrainian language update

Add composer scripts for checking coding standards and running tests

Thanks to Fariskhi Vidyan for the report and assistance, and Tidelift for support.

PHPMailer 6.4.0

This is a maintenance release. The changes introduced in 6.3.0 for setting an envelope sender automatically when using mail() caused problems, especially in WordPress, so this change has been reverted. It gets a minor version bump as it's a change in behaviour, but only back to what 6.2.0 did. See #2298 for more info.

Other changes:

Check for the mbstring extension before decoding addresss in parseAddress, so it won't fail if you don't have it installed

Add Serbian Latin translation (sr_latn)

Enrol PHPMailer in Tidelift, because supporting open-source is important!

PHPMailer 6.3.0

This is a maintenance release.

Handle early connection errors such as 421 during connection and EHLO states

Switch to Github Actions for CI

Generate debug output for mail(), sendmail, and qmail transports. Enable using the same mechanism as for SMTP: set SMTPDebug > 0

Make the mail() and sendmail transports set the envelope sender the same way as SMTP does, i.e. use whatever From is set to, only falling back to the sendmail_from php.ini setting if From is unset. This avoids errors from the mail() function if Sender is not set explicitly and php.ini is not configured. This is a minor functionality change, so bumps the minor version number.

Extend parseAddresses to decode encoded names, improve tests

Changelog

Sourced from phpmailer/phpmailer's changelog.

Version 6.5.0 (June 16th, 2021)

SECURITY Fixes CVE-2021-34551, a complex RCE affecting Windows hosts. See https://github.com/PHPMailer/PHPMailer/blob/master/SECURITY.md for details.

The fix for this issue changes the way that language files are loaded. While they remain in the same PHP-like format, they are processed as plain text, and any code in them will not be run, including operations such as concatenation using the . operator.

Deprecation The current translation file format using PHP arrays is now deprecated; the next major version will introduce a new format.

SECURITY Fixes CVE-2021-3603 that may permit untrusted code to be run from an address validator. See https://github.com/PHPMailer/PHPMailer/blob/master/SECURITY.md for details.

The fix for this issue includes a minor BC break: callables injected into validateAddress, or indirectly through the $validator class property, may no longer be simple strings. If you want to inject your own validator, provide a closure instead of a function name.

Haraka message ID strings are now recognised

Version 6.4.1 (April 29th, 2021)

SECURITY Fixes CVE-2020-36326, a regression of CVE-2018-19296 object injection introduced in 6.1.8, see SECURITY.md for details

Reject more file paths that look like URLs, matching RFC3986 spec, blocking URLS using schemes such as ssh2

Ensure method signature consistency in doCallback calls

Ukrainian language update

Add composer scripts for checking coding standards and running tests

Version 6.4.0 (March 31st, 2021)

Revert change that made the mail() and sendmail transports set the envelope sender if one isn't explicitly provided, as it causes problems described in PHPMailer/PHPMailer#2298

Check for mbstring extension before decoding addresss in parseAddress

Add Serbian Latin translation (sr_latn)

Enrol PHPMailer in Tidelift

Version 6.3.0 (February 19th, 2021)

Handle early connection errors such as 421 during connection and EHLO states

Switch to Github Actions for CI

Generate debug output for mail(), sendmail, and qmail transports. Enable using the same mechanism as for SMTP: set SMTPDebug > 0

Make the mail() and sendmail transports set the envelope sender the same way as SMTP does, i.e. use whatever From is set to, only falling back to the sendmail_from php.ini setting if From is unset. This avoids errors from the mail() function if Sender is not set explicitly and php.ini is not configured. This is a minor functionality change, so bumps the minor version number.

Extend parseAddresses to decode encoded names, improve tests

Commits

a5b5c43 Changelog

e121da3 Merge branch 'master' of https://github.com/PHPMailer/PHPMailer

74e512a Security update

acd264b Merge branch 'CVE-2021-34551'

0063f83 Changelog

707205f Changelog

1047838 Changelog

c2f191b Changelog

45f3c18 Deny string-based callables altogether

6334bab CVE docs

Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR

@dependabot recreate will recreate this PR, overwriting any edits that have been made to it

@dependabot merge will merge this PR after your CI passes on it

@dependabot squash and merge will squash and merge this PR after your CI passes on it

@dependabot cancel merge will cancel a previously requested merge and block automerging

@dependabot reopen will reopen this PR if it is closed

@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot use these labels will set the current labels as the default for future PRs for this repo and language

@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language

@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language

@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

dependencies
opened by dependabot[bot] 0
build(deps): bump phpmailer/phpmailer from 5.2.27 to 6.1.6
Bumps phpmailer/phpmailer from 5.2.27 to 6.1.6.

Release notes

Sourced from phpmailer/phpmailer's releases.

PHPMailer 6.1.6

This is a security release, with some other minor changes. For full details, refer to the advisory.

SECURITY Fix insufficient output escaping bug in file attachment names. CVE-2020-13625. Reported by Elar Lang of Clarified Security.

Correct Armenian ISO language code from am to hy, add mapping for fallback

Use correct timeout property in debug output

PHPMailer 6.1.5

This is a maintenance release.

Reject invalid custom headers that are empty or contain breaks

Various fixes for DKIM issues, especially when using mail() transport

Drop the l= length tag from DKIM signatures; it's a mild security risk

Ensure CRLF is used explicitly when needed, rather than static::$LE

Add a method for trimming header content consistently

Some minor tweaks to resolve static analyser complaints

Check that attachment files are readable both when adding and when sending

Work around Outlook bug in mishandling MIME preamble

Danish translation improvements

PHPMailer 6.1.4

The RFC2047 folding added in 6.1.0 was a little overenthusiastic; It will now only happen when header lines exceed 998 chars.

Clean up hostname handling

Avoid IDN error on older PHP versions, prep for PHP 8.0

Don't force RFC2047 folding unnecessarily

Enable tests on full release of PHP 7.4

PHPMailer 6.1.3

Fix an issue preventing injected debug handlers from working

Fix an issue relating to connection timeout

Add SMTP::MAX_REPLY_LENGTH constant

Remove some dev dependencies; phpdoc no longer included

Fix an issue where non-compliant servers returning bare codes caused an SMTP hang

PHPMailer 6.1.2

Substantial revision of DKIM header generation

Use shorter hashes for auto-generated CID values

Fix format of content-id headers, and only use them for inline attachments

Remove all use of XHTML

Lots of coding standards cleanup

API docs are now auto-updated via GitHub actions

Fix header separation bug created in 6.1.1

Fix misidentification of background attributes in SVG images in msgHTML

PHPMailer 6.1.1

No code changes, just retagging for a misordered commit for 6.1.0.

PHPMailer 6.1.0
... (truncated)

Changelog

Sourced from phpmailer/phpmailer's changelog.

Version 6.1.6 (May 27th, 2020)

SECURITY Fix insufficient output escaping bug in file attachment names. CVE-2020-13625. Reported by Elar Lang of Clarified Security.

Correct Armenian ISO language code from am to hy, add mapping for fallback

Use correct timeout property in debug output

Version 6.1.5 (March 14th, 2020)

Reject invalid custom headers that are empty or contain breaks

Various fixes for DKIM issues, especially when using mail() transport

Drop the l= length tag from DKIM signatures; it's a mild security risk

Ensure CRLF is used explicitly when needed, rather than static::$LE

Add a method for trimming header content consistently

Some minor tweaks to resolve static analyser complaints

Check that attachment files are readable both when adding and when sending

Work around Outlook bug in mishandling MIME preamble

Danish translation improvements

Version 6.1.4 (December 10th, 2019)

Clean up hostname handling

Avoid IDN error on older PHP versions, prep for PHP 8.0

Don't force RFC2047 folding unnecessarily

Enable tests on full release of PHP 7.4

Version 6.1.3 (November 21st, 2019)

Fix an issue preventing injected debug handlers from working

Fix an issue relating to connection timeout

Add SMTP::MAX_REPLY_LENGTH constant

Remove some dev dependencies; phpdoc no longer included

Fix an issue where non-compliant servers returning bare codes caused an SMTP hang

Version 6.1.2 (November 13th, 2019)

Substantial revision of DKIM header generation

Use shorter hashes for auto-generated CID values

Fix format of content-id headers, and only use them for inline attachments

Remove all use of XHTML

Lots of coding standards cleanup

API docs are now auto-updated via GitHub actions

Fix header separation bug created in 6.1.1

Fix misidentification of background attributes in SVG images in msgHTML

Version 6.1.1 (September 27th 2019)

Fix misordered version tag

Version 6.1.0 (September 27th 2019)

Multiple bug fixes for folding of long header lines, thanks to @caugner

Add support for RFC2387 child element content-type hint in multipart/related structures.

Support for Ical event methods other than REQUEST, thanks to @puhr-mde

Change header folding and param separation to use spaces instead of tabs

Use ; to separate multiple MIME header params

Add support for RFC3461 DSN messages

IMAP example code fixed

... (truncated)

Commits

c2796cb Merge pull request from GHSA-f7hx-fqxw-rvvj

a7f1b23 Add funding info

5b63b39 Fix typos (#2037)

c1c38e3 Correct Armenian language code

a12c95e Use correct timeout property in debug output, clarify debug output, see #2018

a8bf068 6.1.5

2e72725 Rewrite and extension of translation (#1989)

55e0b34 Fix issue #2008 - MS Outlook corrupts formatting multipart EML files (#2009)

a55152f Typo fix for #2007

e9710ee Update README.md (#2004)

Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR

@dependabot recreate will recreate this PR, overwriting any edits that have been made to it

@dependabot merge will merge this PR after your CI passes on it

@dependabot squash and merge will squash and merge this PR after your CI passes on it

@dependabot cancel merge will cancel a previously requested merge and block automerging

@dependabot reopen will reopen this PR if it is closed

@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot use these labels will set the current labels as the default for future PRs for this repo and language

@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language

@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language

@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

dependencies
opened by dependabot[bot] 0
build(deps): bump phpmailer/phpmailer from 5.2.27 to 6.1.6
Bumps phpmailer/phpmailer from 5.2.27 to 6.1.6.

Release notes

Sourced from phpmailer/phpmailer's releases.

PHPMailer 6.1.6

This is a security release, with some other minor changes. For full details, refer to the advisory.

SECURITY Fix insufficient output escaping bug in file attachment names. CVE-2020-13625. Reported by Elar Lang of Clarified Security.

Correct Armenian ISO language code from am to hy, add mapping for fallback

Use correct timeout property in debug output

PHPMailer 6.1.5

This is a maintenance release.

Reject invalid custom headers that are empty or contain breaks

Various fixes for DKIM issues, especially when using mail() transport

Drop the l= length tag from DKIM signatures; it's a mild security risk

Ensure CRLF is used explicitly when needed, rather than static::$LE

Add a method for trimming header content consistently

Some minor tweaks to resolve static analyser complaints

Check that attachment files are readable both when adding and when sending

Work around Outlook bug in mishandling MIME preamble

Danish translation improvements

PHPMailer 6.1.4

The RFC2047 folding added in 6.1.0 was a little overenthusiastic; It will now only happen when header lines exceed 998 chars.

Clean up hostname handling

Avoid IDN error on older PHP versions, prep for PHP 8.0

Don't force RFC2047 folding unnecessarily

Enable tests on full release of PHP 7.4

PHPMailer 6.1.3

Fix an issue preventing injected debug handlers from working

Fix an issue relating to connection timeout

Add SMTP::MAX_REPLY_LENGTH constant

Remove some dev dependencies; phpdoc no longer included

Fix an issue where non-compliant servers returning bare codes caused an SMTP hang

PHPMailer 6.1.2

Substantial revision of DKIM header generation

Use shorter hashes for auto-generated CID values

Fix format of content-id headers, and only use them for inline attachments

Remove all use of XHTML

Lots of coding standards cleanup

API docs are now auto-updated via GitHub actions

Fix header separation bug created in 6.1.1

Fix misidentification of background attributes in SVG images in msgHTML

PHPMailer 6.1.1

No code changes, just retagging for a misordered commit for 6.1.0.

PHPMailer 6.1.0
... (truncated)

Changelog

Sourced from phpmailer/phpmailer's changelog.

Version 6.1.6 (May 27th, 2020)

SECURITY Fix insufficient output escaping bug in file attachment names. CVE-2020-13625. Reported by Elar Lang of Clarified Security.

Correct Armenian ISO language code from am to hy, add mapping for fallback

Use correct timeout property in debug output

Version 6.1.5 (March 14th, 2020)

Reject invalid custom headers that are empty or contain breaks

Various fixes for DKIM issues, especially when using mail() transport

Drop the l= length tag from DKIM signatures; it's a mild security risk

Ensure CRLF is used explicitly when needed, rather than static::$LE

Add a method for trimming header content consistently

Some minor tweaks to resolve static analyser complaints

Check that attachment files are readable both when adding and when sending

Work around Outlook bug in mishandling MIME preamble

Danish translation improvements

Version 6.1.4 (December 10th, 2019)

Clean up hostname handling

Avoid IDN error on older PHP versions, prep for PHP 8.0

Don't force RFC2047 folding unnecessarily

Enable tests on full release of PHP 7.4

Version 6.1.3 (November 21st, 2019)

Fix an issue preventing injected debug handlers from working

Fix an issue relating to connection timeout

Add SMTP::MAX_REPLY_LENGTH constant

Remove some dev dependencies; phpdoc no longer included

Fix an issue where non-compliant servers returning bare codes caused an SMTP hang

Version 6.1.2 (November 13th, 2019)

Substantial revision of DKIM header generation

Use shorter hashes for auto-generated CID values

Fix format of content-id headers, and only use them for inline attachments

Remove all use of XHTML

Lots of coding standards cleanup

API docs are now auto-updated via GitHub actions

Fix header separation bug created in 6.1.1

Fix misidentification of background attributes in SVG images in msgHTML

Version 6.1.1 (September 27th 2019)

Fix misordered version tag

Version 6.1.0 (September 27th 2019)

Multiple bug fixes for folding of long header lines, thanks to @caugner

Add support for RFC2387 child element content-type hint in multipart/related structures.

Support for Ical event methods other than REQUEST, thanks to @puhr-mde

Change header folding and param separation to use spaces instead of tabs

Use ; to separate multiple MIME header params

Add support for RFC3461 DSN messages

IMAP example code fixed

... (truncated)

Commits

c2796cb Merge pull request from GHSA-f7hx-fqxw-rvvj

a7f1b23 Add funding info

5b63b39 Fix typos (#2037)

c1c38e3 Correct Armenian language code

a12c95e Use correct timeout property in debug output, clarify debug output, see #2018

a8bf068 6.1.5

2e72725 Rewrite and extension of translation (#1989)

55e0b34 Fix issue #2008 - MS Outlook corrupts formatting multipart EML files (#2009)

a55152f Typo fix for #2007

e9710ee Update README.md (#2004)

Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR

@dependabot recreate will recreate this PR, overwriting any edits that have been made to it

@dependabot merge will merge this PR after your CI passes on it

@dependabot squash and merge will squash and merge this PR after your CI passes on it

@dependabot cancel merge will cancel a previously requested merge and block automerging

@dependabot reopen will reopen this PR if it is closed

@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot use these labels will set the current labels as the default for future PRs for this repo and language

@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language

@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language

@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

dependencies
opened by dependabot[bot] 0
build(deps): bump phpmailer/phpmailer from 5.2.23 to 5.2.27
Bumps phpmailer/phpmailer from 5.2.23 to 5.2.27.

Release notes

Sourced from phpmailer/phpmailer's releases.

PHPMailer 5.2.27

SECURITY Fix potential object injection vulnerability. CVE-2018-19296. Reported by Sehun Oh of cyberone.kr.

Note that the 5.2 branch is deprecated and will not receive security updates after 31st December 2018.

PHPMailer 5.2.26

Minor security backport from 6.0 - set Debugoutput in constructor according to SAPI in use, avoiding potential XSS in default debug output. Thanks to Bankde Eakasit for spotting it.

PHPMailer 5.2.25

Make obtaining SMTP transaction ID more reliable

Add Bosnian translation

This is the last official release in the legacy PHPMailer 5.2 series; there may be future security patches (which will be found in the 5.2-stable branch), but no further non-security PRs or issues will be accepted. Migrate to PHPMailer 6.0.

PHPMailer 5.2.24

SECURITY Fix XSS vulnerability in one of the code examples, CVE-2017-11503. The code_generator.phps example did not filter user input prior to output. This file is distributed with a .phps extension, so it it not normally executable unless it is explicitly renamed, so it is safe by default. There was also an undisclosed potential XSS vulnerability in the default exception handler (unused by default). Patches for both issues kindly provided by Patrick Monnerat of the Fedora Project.

Handle bare codes (an RFC contravention) in SMTP server responses

Make message timestamps more dynamic - calculate the date separately for each message

Include timestamps in HTML-format debug output

Improve Turkish, Norwegian, Serbian, Brazilian Portuguese & simplified Chinese translations

Correction of Serbian ISO language code from sr to rs

Fix matching of multiple entries in Host to match IPv6 literals without breaking port selection (see #1094, caused by a3b4f6b)

Better capture and reporting of SMTP connection errors

Changelog

Sourced from phpmailer/phpmailer's changelog.

Version 5.2.27 (November 14th 2018)

SECURITY Fix potential object injection vulnerability. Reported by Sehun Oh of cyberone.kr.

Note that the 5.2 branch is now deprecated and will not receive security updates after 31st December 2018.

Version 6.0.5 (March 27th 2018)

Re-roll of 6.0.4 to fix missed version file entry. No code changes.

Version 6.0.4 (March 27th 2018)

Add some modern MIME types

Add Hindi translation (thanks to @dextel2)

Improve composer docs

Fix generation of path to language files

Version 6.0.3 (January 5th 2018)

Correct DKIM canonicalization of line breaks for header & body - thanks to @themichaelhall

Make dependence on ext-filter explicit in composer.json

Version 6.0.2 (November 29th 2017)

Don't make max line length depend on line break format

Improve Travis-CI config - thanks to Filippo Tessarotto

Match SendGrid transaction IDs

idnSupported() now static, as previously documented

Improve error messages for invalid addresses

Improve Indonesian translation (thanks to @januridp)

Improve Esperanto translation (thanks to @dknacht)

Clean up git export ignore settings for production and zip bundles

Update license doc

Updated upgrading docs

Clarify addStringEmbeddedImage docs

Hide auth credentials in all but lowest level debug output, prevents leakage in bug reports

Code style cleanup

Version 6.0.1 (September 14th 2017)

Use shorter Message-ID headers (with more entropy) to avoid iCloud blackhole bug

Switch to Symfony code style (though it's not well defined)

CI builds now apply syntax & code style checks, so make your PRs tidy!

CI code coverage only applied on latest version of PHP to speed up builds (thanks to @Slamdunk for these CI changes)

Remove composer.lock - it's important that libraries break early; keeping it is for apps

Rename test scripts to PSR-4 spec

Make content-id values settable on attachments, not just embedded items

Add SMTP transaction IDs to callbacks & allow for future expansion

Expand test coverage

Version 6.0 (August 28th 2017)

This is a major update that breaks backwards compatibility.

Requires PHP 5.5 or later

Uses the PHPMailer\PHPMailer namespace

File structure simplified and PSR-4 compatible, classes live in the src/ folder

The custom autoloader has been removed: use composer!

... (truncated)

Commits

dde1db1 5.2.27

f1231a9 Backport changes for CVE-2018-19296

44776b5 Backport changes for CVE-2018-19296

4874af6 Fix 5.2-stable branch README.md minimal install links that 404 (#1461)

49ae798 Add .github directory to export-ignore (#1261)

22e8a57 Update license file, fixes #1243

7036299 5.2.26

b6316bb Switch debug output according to SAPI

b6eadbe minor typo change (#1222)

d914f73 Travis-CI no longer supports PHP 5.3, so remove it

Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR

@dependabot recreate will recreate this PR, overwriting any edits that have been made to it

@dependabot merge will merge this PR after your CI passes on it

@dependabot squash and merge will squash and merge this PR after your CI passes on it

@dependabot cancel merge will cancel a previously requested merge and block automerging

@dependabot reopen will reopen this PR if it is closed

@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot use these labels will set the current labels as the default for future PRs for this repo and language

@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language

@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language

@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

dependencies
opened by dependabot[bot] 0
implement custom page and article list endpoint

Add the following API endpoint: /de/daten/page?url=artikel/wandelhalle-persoenlich-burson-marsteller-stockt&load-entity-refs=taxonomy_term,file /de/daten/articles?limit=10&page=0

This is a simple version of restws and restws_entityreference built into the lobbywatch_meta sub-module. But hopefully circumventing the url resolving issues in production that we're having with them.

opened by tpreusse 0
Datenbereinigung: Interessebindungen zu parlamentarischen Gruppen
[ ] Viele dieser Interessebindungen haben ein von-Datum vom 09.06.2020. dies sollte vermutlich auf null gesetzt werden.

[ ] Deklarationspflicht und -status müsste man sich bei diesen Interessebindungen auch überlegen und dann einheitlich gleich machen (bei manuell erfassten nicht immer gleich).

[ ] Der Datenimport müsste sich dann auch daran halten, wobei das von-Datum hier gesetzt werden kann, da dieser Import nun periodisch läuft. Obwohl sich hier auch noch die Frage stellt wie neu erfasste Personen von Import-Prozessen gehandhabt werden.
opened by knutwannheden 3
Partei- und Fraktionszugehörigkeit historisieren

Für historische Auswertungen ist eine Aufschlüsselung nach Partei oder Fraktion sehr oft interessant. In der Lobbywatch Datenbank ist das aktuell nur bedingt möglich, da die Partei- und Fraktionszugehörigkeit nicht historisiert werden und diese ändern kann. Die Fraktionszugehörigkeit kann öfter ändern bei der Regierungsbildung in einer neuen Legislatur aber auch Parteifusionen, wie die von CVP und BDP, würden eine Historisierung benötigen, um korrekte Auswertungen zu ermöglichen. In Einzelfällen haben Parlamentarier sogar Partei gewechselt.

Der Vorschlag wäre, dass man wie bei der Kommissionsmitgliedschaft eine Assoziationstabelle einführen würde. Damit könnten dann auch Rollen wie Fraktionspräsidium abgebildet und festgehalten werden.

Diese Daten sind via der ws.parlament.ch Schnittstelle verfügbar (nicht geprüft wie es mit ws-old.parlament.ch aussieht) und könnten jedenfalls für einen Initialimport verwendet werden.

opened by knutwannheden 7
feat(DB): Add new v_abgegrenzte_interessenbindung view

Adds a new database view v_abgegrenzte_interessenbindung which in contrast to the interessebindung table has the columns von_effektiv and bis_effektiv to represent the start and end date for the validity period (as opposed to von and bis). These dates are never null and when the end date is yet unknown (open-ended) the bis_effektiv will be represented by the date 9999-12-31.

The value for von_effektiv will correspond to von when given and otherwise to freigabe_datum or parlamentarier.im_rat_seit, in case the interessebindung row was created as part of the initial research of the politician.

Also note that in case a politician was elected for two non-consecutive periods of time (cf. parlamentarier.ratsunterbruch_von and parlamentarier.ratsunterbruch_bis), then the same interessebindung object may (depending on von and bis) end up being represented by multiple rows in this view (both with the same value for interessebindung_id).

Related: #18

opened by knutwannheden 0
Datenmodellierung problematisch für Ermittlung von Start- und End-Date von Interessebindungen
Da Interessebindungen mehrheitlich "manuell" recherchiert werden müssen und im Internet oft Details fehlen, sind die bei Lobbywatch verzeichneten Interessebindungen oft nur teilweise erfasst. Z.B. gibt es oft kein Start- und End-Date (entspricht in der Datenbank interessebindung.von und interessebindung.bis). Für Auswertungen, welche sich auf das aktuelle Datum ("heute") ist das meist unproblematisch, da man davon ausgehen kann, dass die Interessebindung "gültig" ist auch wenn Start- und End-Date nicht vorhanden sind.

Anders sieht dies bei historischen Auswertungen aus. Ein Beispiel einer historischer Auswertung wäre, wenn man die zeitliche Entwicklung der Anzahl Interessebindungen einer gegebenen Branche, Partei, Rechtsform oder anderer Teilmenge grafisch darstellen will. Hierbei muss jedes Datum auf der Zeitachse als Referenzdatum verwendet werden und die "aktiven" Interessebindungen müssen jeweils aus diesem Blickwinkel zusammengesucht werden.

Es gibt hierbei mehrere Sachen zu beachten:

Grundsätzlich sind Interessebindungen nur als solche zu betrachten während der Amtszeit des Parlamentariers (siehe parlamentarier.im_rat_seit und parlamentarier.im_rat_bis in der Datenbank). D.h. wenn z.B. eine Interessebindung kein End-Date hat, dann ist dieses implizit durch den Rücktritt des Parlamentariers (also parlamentarier.im_rat_bis) gegeben.

Beim Start-Date ist die Situation etwas komplizierter. Wenn ein Parlamentarier neu erfasst wird, werden dessen Interessebindungen recherchiert und eingetragen. Bei diesen ist dann oft das Start-Date auch nicht bekannt. Man geht aber davon aus, dass der Parlamentarier alle diese Interessebindungen ins Amt "mit sich mitgebracht" hat, da diese Recherche in der Regel sehr zeitnah geschieht. D.h. diese Interessebindungen haben dann auch implizit den Amtsantritt als Start-Date. Diese Interessebindungen der ersten Recherche sind aber in der Datenbank nicht speziell gekennzeichnet. Man kann sie indirekt erkennen, da sie alle das selbe Freigabedatum (in der Datenbank interessebindung.freigabe_datum und dies ist ein Datum mit Zeitstempel) aufweisen, welches logischerweise auch das früheste Freigabedatum für den Parlamentarier ist.

Wenn nun nachträglich (also nach der ersten Erfassung) zusätzliche Interessebindungen auftauchen, dann ist bei diesen oft auch kein Start-Date bekannt. Es ist zwar gut möglich, dass der Parlamentarier diese bereits bei Amtsantritt hatte, aber für Lobbywatch macht es trotzdem Sinn diese als "neue" Interessebindungen zu betrachten und deshalb wird dann das Freigabedatum als Start-Date verwendet.

Letztlich muss bei diesen historischen Auswertungen auch beachtet werden, dass die parlamentarier.im_rat_seit und parlamentarier.im_rat_bis in der Datenbank dem ersten und letzten Antsantritt bzw. -austritt entsprechen. Wenn der Parlamentarier während dieser Zeitspanne mal "abgewählt" und dann wieder neu gewählt wurde, dann wird dies in der Datenbank als Ratsunterbruch geführt (siehe parlamentarier.ratsunterbruch_von and parlamentarier.ratsunterbruch_bis). Während diesem Ratsunterbruch gilt dann eine Interessebindung auch nicht als "aktiv".

Mit der aktuellen Datenmodellierung sind historische Auswertungen der Interessebindungen komplex zu implementieren, da es schwierig ist zu ermitteln, welches Start- und End-Date für eine Interessebindung gültig sind relativ zu einem gegebenen Referenzdatum. Wie sich aus den Punkten oben ergibt, kann für eine Interessebindung sogar verschiedene Start- und End-Dates gelten, wenn ein Parlamentarier einen Ratsunterbruch hatte: Bei einem Referenzdatum während der ersten Amtszeit sind Amtsantritt und Beginn des Ratsunterbruchs zu beachten (im_rat_seit und ratsunterbruch_von) und während der zweiten Amtszeit gilt es Ende des Ratsunterbruchs und Rücktritt aus dem Parlament zu beachten (ratsunterbruch_bis und im_rat_bis).

Um solche historische Auswertungen einfacher zu machen, sollten wir uns überlegen das Datenmodell anzupassen oder alternativ vielleicht nur mit Views zu unterstützen. Die möglichen Lösungen können im Rahmen dieser Issue diskutiert werden.
opened by knutwannheden 7