Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8550619
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 11, 20262026-06-11T13:59:27+00:00 2026-06-11T13:59:27+00:00

Our server recently had an update done (PHP was updated from 5.2.x to 5.3.14)

  • 0

Our server recently had an update done (PHP was updated from 5.2.x to 5.3.14)
Because of this update we cannot use our custom Locale class that is being run by __autoload()
From my understanding this is caused by a Locale class existing some where in the “PEAR”

Is there a way for me to resolve this conflict issue without changing my class name from Locale to something else (basically some how force the PEAR locale not to load or ignore it just for the Locale request)?

Thanks

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-11T13:59:28+00:00Added an answer on June 11, 2026 at 1:59 pm

    Since Locale is now a native PHP class, you can’t override it directly, which is why your code no longer works.

    Solutions:

    1. Rebuild you copy of PHP so it doesn’t include the Locale module. Probably not a good idea, and definitely bad for compatiblity, but could be considered if you’re desperate.

    2. Rename your class. There are refactoring tools that can make this sort of thing fairly easy.

    3. Use PHP 5.3’s namespace feature to give your Locale class a different namespace to the built-in Locale class. Add a namespace clause to the top of your class file, and use your namespace wherever you want to reference your Locale class rather than the built-in one.

    The choice between 2 and 3 is up to you. I’d suggest 2, since your class probably isn’t functionally similar to the PHP one, so you’ll want to distance yourself from it. But the namespace solution is also an option if you want to keep your current classname.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Our dev server was recently upgraded to PHP v5.2.13. With that upgrade we have
We recently moved our database from our SQL Server 2005 server to our SQL
We recently had our TFS 2008 server go down. It was rebuilt with TFS
We have just recently got our SVN server installed. My developers have added the
Our application uses a SQL Server back-end with many stored procedures. Recently, while trying
Recently I had this question , and everything worked properly until I sent it
We recently went into private beta on our flagship product and had a small
We recently got a call from one of our clients, complaining that their site
We have recently moved to a new web server (from IIS6 to IIS7.5) and
We recently added a feature to our software that requires .NET 2.0 SP2. This

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.