Error: Class "PublicStream" not found in _pathologic_replace() (line 208 of pathologic.module)

Created on 8 February 2024, 5 months ago
Updated 28 February 2024, 4 months ago

Problem/Motivation

After switching to PHP 8.1 and Drupal core to 9.5 and updating the module to the latest version, we are getting this error.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

💬 Support request
Status

Fixed

Version

2.0

Component

Code

Created by

🇮🇳India binnythomas Trivandrum, Kerala, India

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @binnythomas
  • Assigned to abhishek_virasat
  • Issue was unassigned.
  • First commit to issue fork.
  • 🇪🇸Spain bletch

    Make sure you have the actual correct code from alpha2. If you have a previous version that has been patched it is best to remove and re-require the module (with the patch deleted from composer.json if you no longer need it).

    Please ignore my merge request. I realised pretty quickly that the code on my local did not match what was actually in alpha2. When I got the correct code this issue resolved.

  • 🇺🇸United States dww

    Yeah, if there were a fatal error simply from installing the new version, our automated tests would have failed before I tagged the release. I think this is a support request about an incomplete upgrade to a new version. As folks have said, if you're having trouble, and a drush cr doesn't solve it, try this:

    composer remove drupal/pathologic
    composer require drupal/pathologic
    

    (or equivalent).

  • Status changed to Fixed 5 months ago
  • 🇺🇸United States dww

    More to the point, grepping the source tree for 'PublicStream' returns no hits with the 2.0.x branch. The only place I see that is in patches for 🐛 Internal URL handling (language prefixes, base://, ...) Needs work . So this is clearly coming from incomplete patching or something. Calling this fixed.

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.69.0 2024