Skip to content

Rebase on google upstream#1

Closed
zorglube wants to merge 23 commits intoCube707:mainfrom
zorglube:rebase-on-google-upstream
Closed

Rebase on google upstream#1
zorglube wants to merge 23 commits intoCube707:mainfrom
zorglube:rebase-on-google-upstream

Conversation

@zorglube
Copy link

@zorglube zorglube commented Feb 9, 2026

Hello @Cube707

I'm working on the integration of Matomo on my PHPBB forum.
I found you plugin, and I thought it need an update based on th evolution of the origin : https://github.com/phpbb-extensions/googleanalytics

Hop my PR is good,
BR

@zorglube zorglube marked this pull request as draft February 9, 2026 16:00
@zorglube zorglube marked this pull request as ready for review February 10, 2026 12:19
@Cube707
Copy link
Owner

Cube707 commented Feb 10, 2026

Sorry but this can't be merged, the history is quite mangled. Please reset to current master and Marge the upstream changes cleanly. (If you don't know how I can give some more pointers or do it later today myself)

Then open a separate PR for your addition.

Thanks

@zorglube
Copy link
Author

Sorry but this can't be merged, the history is quite mangled. Please reset to current master and Marge the upstream changes cleanly. (If you don't know how I can give some more pointers or do it later today myself)

Do you mean squash the commis ?

@zorglube zorglube force-pushed the rebase-on-google-upstream branch from ee796d4 to 511557f Compare February 10, 2026 14:33
@zorglube zorglube closed this Feb 10, 2026
@zorglube zorglube force-pushed the rebase-on-google-upstream branch from 08f6d2f to 6300548 Compare February 10, 2026 14:38
@zorglube zorglube reopened this Feb 10, 2026
@zorglube zorglube force-pushed the rebase-on-google-upstream branch 2 times, most recently from 1f4461a to 5c1cf99 Compare February 10, 2026 15:27
@zorglube
Copy link
Author

@Cube707 Is this better now ?

@Cube707
Copy link
Owner

Cube707 commented Feb 10, 2026

No your still recreating commit which already exists in this repo. You need to reset to this repos current master before merging upstream.

I can writeup an example once I am done at work

@Cube707
Copy link
Owner

Cube707 commented Feb 10, 2026

heres what you need to do:

  1. ensure you have all repos configured as remotes, your fork, this repo and the upstream for google. Skip what you already have and replace the names accordingly in the later steps
    git remote add Cube707 https://github.com/Cube707/phpbb-matomoanalytics.git
    git remote add upstream https://github.com/phpbb-extensions/googleanalytics.git
  2. ensure you are up to date with all remotes:
    git fetch upstream
    git fetch Cube707
  3. reset you branch to get a clean starting state (IMPORTANT: this is a destructive action which removes commit. Save all work you want to keep on separate branches)
    git reset --hard Cube707/main
  4. merge the updates from the upstream
    git merge upstream/master
    this will most likely have merge-conflicts you need to solve
  5. now you can update this PR
    git push --force

Note that this doesn't yet include your modifications, those should be a separate PR

@Cube707
Copy link
Owner

Cube707 commented Feb 10, 2026

your your new commit, separate it back into multiple commits, each one on topic. And than create new PRs for your additions.

Here also don't mix concerns, a typos in the existing text are seperate from adding new stuff and can probably be merged much faster and without discussion, so they should be separate PRs. Also deleting stuff needs a good reason.

You should also note that I will not merge changes to the pre-exisitng google-analytics code, for that you would need to open a PR upstream and I will sync my fork once the upstream accepted the merge. I can offer you to provide a feature branch and a pre-release version if you want it quickly in the matomo version.

@zorglube
Copy link
Author

zorglube commented Feb 10, 2026 via email

@zorglube zorglube closed this Feb 11, 2026
@zorglube zorglube force-pushed the rebase-on-google-upstream branch from 5c1cf99 to 6300548 Compare February 11, 2026 09:43
@zorglube zorglube reopened this Feb 11, 2026
@zorglube
Copy link
Author

@Cube707, you should be happier now.

The work isn't fnished yet. Please, tell me if I'm on the wright path.

@Cube707
Copy link
Owner

Cube707 commented Feb 11, 2026

This looks much better, I will review the details later

Signed-off-by: Zorglube <630192+zorglube@users.noreply.github.com>
@zorglube zorglube force-pushed the rebase-on-google-upstream branch from 7e17487 to b74f2c9 Compare February 11, 2026 15:08
@zorglube
Copy link
Author

This looks much better, I will review the details later

Ready for review.

Copy link
Owner

@Cube707 Cube707 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are changes to event/listener.php missing from the merge.

I also think we should keep the feature which adds a paragraph about the tracking-tool beeping used. I suggest merging the Google-Analytics text an then rewriting it to match matomo as a new commit

name: Extension tests
uses: phpbb-extensions/test-framework/.github/workflows/tests.yml@3.3.x
with:
EXTNAME: phpbb/googleanalytics # Your extension vendor/package name
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This needs to be the correct extension name

composer.json Outdated
"email": "mail@janwille.de",
"homepage": "https://janwille.de",
"role": "Extension Developer"
"role": "Upstream Extension Developer"
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is me 😄

It can stay as "Extension developer"

@@ -0,0 +1,50 @@
<?php
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please don't add in your own addition into the merge, open a separate PR for new features

}

/**
/**
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What changed here? Please don't commit whitespace changes

zorglube added a commit to zorglube/phpbb-matomoanalytics that referenced this pull request Feb 12, 2026
 - Cube707#1 (comment)
 - Cube707#1 (comment)
 - Cube707#1 (comment)

Signed-off-by: Zorglube <630192+zorglube@users.noreply.github.com>
 - Cube707#1 (comment)
 - Cube707#1 (comment)
 - Cube707#1 (comment)
 - Cube707#1 (comment)

Signed-off-by: Zorglube <630192+zorglube@users.noreply.github.com>
@zorglube zorglube force-pushed the rebase-on-google-upstream branch from 6199449 to 407b726 Compare February 12, 2026 10:48
zorglube added a commit to zorglube/phpbb-matomoanalytics that referenced this pull request Feb 12, 2026
 - Cube707#1 (review)

Signed-off-by: Zorglube <630192+zorglube@users.noreply.github.com>
@zorglube
Copy link
Author

There are changes to event/listener.php missing from the merge.

I also think we should keep the feature which adds a paragraph about the tracking-tool beeping used. I suggest merging the Google-Analytics text an then rewriting it to match matomo as a new commit

I'm note sure the correction for that part is good, you should pay attention on this one.

zorglube added a commit to zorglube/phpbb-matomoanalytics that referenced this pull request Feb 12, 2026
 - Cube707#1 (review)

Signed-off-by: Zorglube <630192+zorglube@users.noreply.github.com>
@zorglube zorglube force-pushed the rebase-on-google-upstream branch from ffb1769 to 67a60a2 Compare February 12, 2026 11:39
 - Cube707#1 (review)

Signed-off-by: Zorglube <630192+zorglube@users.noreply.github.com>
@zorglube zorglube force-pushed the rebase-on-google-upstream branch from 67a60a2 to 51ea72e Compare February 12, 2026 11:41
//

$lang = array_merge($lang, [
'PHPBB_ANALYTICS_PRIVACY_POLICY' => '
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry @Cube707 I don't speak German enough, can you translate please ?

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will do.

*/
public function append_agreement()
{
if (!$this->config['googleanalytics_id']
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this needs to reference one of our config settings

return;
}

$this->language->add_lang('googleanalytics_ucp', 'cube/matomoanalytics');
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this needs to reference the correct file

//

$lang = array_merge($lang, [
'PHPBB_ANALYTICS_PRIVACY_POLICY' => '
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will do.

<br><br>
Thoses informations may be transfer to a third parties. To learn more about how the statistics informations are used, contact the website owner.
<br><br>
If you want to opt out of the statistics collection <div id="matomo-opt-out"></div><script src="%1$s/index.php?module=CoreAdminHome&action=optOutJS&div=matomo-opt-out></script>.
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this link will not work, as it references the phpbb domain, which is mostlikely different from the matomo-url.

Hm, I will need to think about how to solve this

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess following the Matomo doc: https://developer.matomo.org/guides/tracking-optout this template should be customised using the parameter MATOMOANALYTICS_URL.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

matomo also has a secion about how to write a privacy notice which could be helpfull for this:

https://matomo.org/faq/how-to/how-to-write-a-gdpr-compliant-privacy-notice/

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I propose, first finish the update, then work on the GDPR notice. Is this ok for you ?

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not sure If we are missunderstanding each other or not, but I only meant we should reference it when transferring the message for matomo. A shorte paragraph about matomo usage is enough same as for google-ananlytics, I just meant we dont have to keep the wording so close to the upstream one and might be better of going more in the direction recommended by matomo

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess you're right, there's a misunderstanding somewhere.

I'll fork your code, follow my ideas, you'll be free to integrate if you like.

Just to make it clear, there absolutely no bad feelings in my words.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wanted to start a branch with some of the current progress, but didn't get to it

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wanted to start a branch with some of the current progress, but didn't get to it

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll try to do so, do not hesitate to participate ;-)

Signed-off-by: Zorglube <630192+zorglube@users.noreply.github.com>
@Cube707
Copy link
Owner

Cube707 commented Feb 13, 2026

I thought about this a bit and decided to push back the discussion and only merge up to f1d39a3 for now. This splits up concenes a but, allows the CI to run properly on master and means we can take a bit more time to work out how to implement the howle privacy notice thing

@Cube707
Copy link
Owner

Cube707 commented Feb 13, 2026

superseded by #5

@Cube707 Cube707 closed this Feb 13, 2026
@Cube707
Copy link
Owner

Cube707 commented Feb 16, 2026

@zorglube just created a release containing the french translation (and the spelling fixes)

I also merged the upstream changes into the branch dev/privacy-information, but won't continue to work on it today. Next steps would be to migrate the googleanalytics_ucp files to matomo and work on the texts as well as the opt-out button.

If you want to add any of your work, feel free to commit them based on that and open a draft-PR, that way we can both work on it (if I open the PR, you won't have access...)

@zorglube
Copy link
Author

@zorglube just created a release containing the french translation (and the spelling fixes)

Whoop Whoop !! \o/

I also merged the upstream changes into the branch dev/privacy-information, but won't continue to work on it today. Next steps would be to migrate the googleanalytics_ucp files to matomo and work on the texts as well as the opt-out button.

If you want to add any of your work, feel free to commit them based on that and open a draft-PR, that way we can both work on it (if I open the PR, you won't have access...)

I'll have a look !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants