doctrine/archived-orm
1
0
Fork 0
mirror of https://github.com/doctrine/orm.git synced 2026-03-24 06:52:09 +01:00
Code Issues 5.3k Packages Projects Releases 100 Wiki Activity

[PR #1046] [CLOSED] Fix the "Erroneous data format for unserializing" error message #9079

New Issue
Open
opened 2026-01-22 16:03:07 +01:00 by admin · 0 comments
admin commented 2026-01-22 16:03:07 +01:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/doctrine/orm/pull/1046
Author: @peterjmit
Created: 6/3/2014
Status: ❌ Closed

Base: 2.3 ← Head: 2.3

📝 Commits (1)

  • 32fd2f3 Fix the "Erroneous data format for unserializing" error message

📊 Changes

1 file changed (+7 additions, -1 deletions)

View changed files

📝 lib/Doctrine/ORM/Mapping/ClassMetadataInfo.php (+7 -1)

📄 Description

Backport patch from PR #1045 to 2.3 branch.

@ocramius - I'm not sure if this is viable, but based on the comments from people it could be helpful to have this fixed in 5.3? I'm not 100% sure whether PHP or Doctrine is at fault here?

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/doctrine/orm/pull/1046 **Author:** [@peterjmit](https://github.com/peterjmit) **Created:** 6/3/2014 **Status:** ❌ Closed **Base:** `2.3` ← **Head:** `2.3` --- ### 📝 Commits (1) - [`32fd2f3`](https://github.com/doctrine/orm/commit/32fd2f386b91615cbb181cee40aedb7b5a0b1366) Fix the "Erroneous data format for unserializing" error message ### 📊 Changes **1 file changed** (+7 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `lib/Doctrine/ORM/Mapping/ClassMetadataInfo.php` (+7 -1) </details> ### 📄 Description Backport patch from PR #1045 to 2.3 branch. @ocramius - I'm not sure if this is viable, but based on the comments from people it could be helpful to have this fixed in 5.3? I'm not 100% sure whether PHP or Doctrine is at fault here? --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
admin added the pull-request label 2026-01-22 16:03:07 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
BC Break
Bug
Can't Fix
Deprecation
Documentation
DQL
Duplicate
Failing Test
Hacktoberfest
Improvement
Improvement
Incomplete
Invalid
Missing Tests
New Feature
PR Created
pull-request
Mirrored from GitHub Pull Request
 Question
Regression
Status: Waiting feedback
Waiting feedback
WIP
Won't Fix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
admin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: doctrine/archived-orm#9079
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?