Skip to content

[ticket/17623] switch twitter to x in profile#6946

Open
Prosk8er wants to merge 2 commits intophpbb:3.3.xfrom
Prosk8er:ticket/17623-phpbb3
Open

[ticket/17623] switch twitter to x in profile#6946
Prosk8er wants to merge 2 commits intophpbb:3.3.xfrom
Prosk8er:ticket/17623-phpbb3

Conversation

@Prosk8er
Copy link
Copy Markdown
Contributor

@Prosk8er Prosk8er commented Mar 14, 2026

phpbb3 version of PHPBB-17623

Checklist:

  • Correct branch: master for new features; 3.3.x for fixes
  • Tests pass
  • Code follows coding guidelines: master and 3.3.x
  • Commit follows commit message format

Tracker ticket:

https://tracker.phpbb.com/browse/PHPBB-17623

phpbb3 version of PHPBB-17623

PHPBB-17623
@github-actions
Copy link
Copy Markdown

github-actions bot commented Mar 14, 2026

The attempt to merge branch 3.3.x into master has completed after considering the changes in this PR.

  • Merge result: Conflict ❌

A separate PR will be needed to merge 3.3.x into master.

@Prosk8er Prosk8er force-pushed the ticket/17623-phpbb3 branch from c2b00e2 to 9c49410 Compare March 14, 2026 11:52
@kaileymsnay
Copy link
Copy Markdown
Contributor

kaileymsnay commented Mar 14, 2026

Part of your failure is your commit message for "forgot migration file". You need [ticket/17623] at the front. Same with your other PR.

@Prosk8er
Copy link
Copy Markdown
Contributor Author

Part of your failure is your commit message for "forgot migration file". You need [ticket/17623] at the front. Same with your other PR.

thanks that was going to be my next try

phpbb3 version of PHPBB-17623

PHPBB-17623
@Prosk8er Prosk8er force-pushed the ticket/17623-phpbb3 branch from 9c49410 to b5b2b00 Compare March 14, 2026 13:38
Copy link
Copy Markdown
Member

@danieltj27 danieltj27 left a comment

Choose a reason for hiding this comment

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

There's still lots of references to Twitter which should be completely changed to say X instead.

Also there needs to be a discussion around the migration schema. I'm pretty sure you should keep old schemas as is and create new ones to update existing data but a second opinion is needed on that.

INSERT INTO phpbb_profile_fields (field_name, field_type, field_ident, field_length, field_minlen, field_maxlen, field_novalue, field_default_value, field_validation, field_required, field_show_novalue, field_show_on_reg, field_show_on_pm, field_show_on_vt, field_show_on_ml, field_show_profile, field_hide, field_no_view, field_active, field_order, field_is_contact, field_contact_desc, field_contact_url) VALUES ('phpbb_yahoo', 'profilefields.type.string', 'phpbb_yahoo', '40', '5', '255', '', '', '.*', 0, 0, 0, 1, 1, 1, 1, 0, 0, 0, 8, 1, 'SEND_YIM_MESSAGE', 'ymsgr:sendim?%s');
INSERT INTO phpbb_profile_fields (field_name, field_type, field_ident, field_length, field_minlen, field_maxlen, field_novalue, field_default_value, field_validation, field_required, field_show_novalue, field_show_on_reg, field_show_on_pm, field_show_on_vt, field_show_on_ml, field_show_profile, field_hide, field_no_view, field_active, field_order, field_is_contact, field_contact_desc, field_contact_url) VALUES ('phpbb_facebook', 'profilefields.type.string', 'phpbb_facebook', '20', '5', '50', '', '', '[\w.]+', 0, 0, 0, 1, 1, 1, 1, 0, 0, 1, 9, 1, 'VIEW_FACEBOOK_PROFILE', 'https://facebook.com/%s/');
INSERT INTO phpbb_profile_fields (field_name, field_type, field_ident, field_length, field_minlen, field_maxlen, field_novalue, field_default_value, field_validation, field_required, field_show_novalue, field_show_on_reg, field_show_on_pm, field_show_on_vt, field_show_on_ml, field_show_profile, field_hide, field_no_view, field_active, field_order, field_is_contact, field_contact_desc, field_contact_url) VALUES ('phpbb_twitter', 'profilefields.type.string', 'phpbb_twitter', '20', '1', '15', '', '', '[\w_]+', 0, 0, 0, 1, 1, 1, 1, 0, 0, 1, 10, 1, 'VIEW_TWITTER_PROFILE', 'https://twitter.com/%s');
INSERT INTO phpbb_profile_fields (field_name, field_type, field_ident, field_length, field_minlen, field_maxlen, field_novalue, field_default_value, field_validation, field_required, field_show_novalue, field_show_on_reg, field_show_on_pm, field_show_on_vt, field_show_on_ml, field_show_profile, field_hide, field_no_view, field_active, field_order, field_is_contact, field_contact_desc, field_contact_url) VALUES ('phpbb_twitter', 'profilefields.type.string', 'phpbb_twitter', '20', '1', '15', '', '', '[\w_]+', 0, 0, 0, 1, 1, 1, 1, 0, 0, 1, 10, 1, 'VIEW_TWITTER_PROFILE', 'https://x.com/%s');
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

You need to replace VIEW_TWITTER_PROFILE with VIEW_X_PROFILE although perhaps it needs to be something a bit more unique as that kind of makes it seem like a placeholder. Up for discussion as to whether that's okay as is but it definitely needs changing from Twitter.

'AUTH_PROVIDER_OAUTH_SERVICE_FACEBOOK' => 'Facebook',
'AUTH_PROVIDER_OAUTH_SERVICE_GOOGLE' => 'Google',
'AUTH_PROVIDER_OAUTH_SERVICE_TWITTER' => 'Twitter',
'AUTH_PROVIDER_OAUTH_SERVICE_TWITTER' => 'X',
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Replace with AUTH_PROVIDER_OAUTH_SERVICE_X

),
'TRACKED_PHP_ERROR' => 'Tracked PHP errors: %s',
'TWITTER' => 'Twitter',
'TWITTER' => 'X',
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Replace language string to X

'VIEW_FACEBOOK_PROFILE' => 'View Facebook Profile',
'VIEW_SKYPE_PROFILE' => 'View Skype Profile',
'VIEW_TWITTER_PROFILE' => 'View Twitter Profile',
'VIEW_TWITTER_PROFILE' => 'View X Profile',
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Replace the word TWITTER


$this->db->sql_query(
"UPDATE $profile_fields
SET field_contact_url = 'https://x.com/%s'
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

A second opinion is probably wise although I'm pretty sure you shouldn't be changing database migrations. This only adds a custom profile field that can be changed in the ACP anyway. I think the most appropriate way to go about this is to create a new migration (possibly).

.phpbb_facebook-icon { background-position: -119px 0; }
.phpbb_skype-icon { background-position: -161px 0; }
.phpbb_twitter-icon { background-position: -203px 0; }
.phpbb_twitter-icon { background-position: -202px 0; }
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Change the class name to x-icon and update all instances where it's used.

@Crizz0
Copy link
Copy Markdown
Member

Crizz0 commented Mar 26, 2026

Maybe it is a better idea to remove it instead of renaming.

@Prosk8er
Copy link
Copy Markdown
Contributor Author

Prosk8er commented Mar 26, 2026

There's still lots of references to Twitter which should be completely changed to say X instead.

Also there needs to be a discussion around the migration schema. I'm pretty sure you should keep old schemas as is and create new ones to update existing data but a second opinion is needed on that.

@danieltj27 i left the vars/strings twitter instead of changing everything to x so its easier to understand what it is plus if i did that there would be a bunch more changes and a single letter for language var like 'X' => 'X', which doesn't seem right to have 1 letter? i could change it all if its deemed necessary

@danieltj27
Copy link
Copy Markdown
Member

@danieltj27 i left the vars/strings twitter instead of changing everything to x so its easier to understand what it is plus if i did that there would be a bunch more changes and a single letter for language var like 'X' => 'X', which doesn't seem right to have 1 letter? i could change it all if its deemed necessary

I don't disagree. Perhaps XCOM would make more sense, it's a bit more descriptive rather than just having X which could be mistaken as a placeholder and changed accidentally.

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.

4 participants