Seems to have incompatibility with Persistent URL module :

"Trying to get property of non-object in purl_path->remove() (line 67 in modules\purl\includes\purl_path.inc)"

Comments

donquixote’s picture

Steps to reproduce?

donquixote’s picture

Status: Active » Postponed (maintainer needs more info)

Also, could you give me a backtrace?
And any hint that this is related to Crumbs?

donquixote’s picture

Status: Postponed (maintainer needs more info) » Needs review
StatusFileSize
new603 bytes

Patch: drupal_get_normal_path() should not be called with FALSE.

Can you test?

donquixote’s picture

Related issue on the purl queue:
#1885538: Notice purl_path.inc Line 67

jesorensen’s picture

This patch did not prevent the errors for me.

donquixote’s picture

Which release did you test on?

donquixote’s picture

Well, it totally fixes it for me.
I can reproduce the error message, and the stack trace clearly points to this piece of code.

This patch looks pretty obvious, I will get it in, and then we can continue to look for further issues.

donquixote’s picture

@jesorensen,
can you provide a stack trace of your own? Ideally using the 7.x-1.9 release, or the latest 7.x-1.x-dev (these are identical atm).

donquixote’s picture

Status: Needs review » Postponed (maintainer needs more info)

Ok, if I get steps to reproduce or a stack trace, we can reopen :)

donquixote’s picture

Status: Postponed (maintainer needs more info) » Fixed

#1885538-5: Notice purl_path.inc Line 67

Hi,
It seems the problem is not really coming from Breadcrumbs module itself since in my case, it is not installed.
I have removed it a long time ago.
Enclosed is the screen-capture of what I've got on my Drupal site.
Any help ?
This issue appeared after activation of securepages module.

Judging from the absence of further reports in this issue, I assume that the Crumbs-related part of the bug has been fixed with the patch.
What remains is bugs in other modules.

I mark this as "fixed" with patch #3.

Status: Fixed » Closed (fixed)

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