We have moved to GitHub Issues
You are viewing the read-only archive of Umbraco's issue tracker. To create new issues, please head over to GitHub Issues.
Make sure to read the blog posts announcing the move for more information.
Created by Mads Jørgensen 29 Jan 2013, 11:08:43 Updated by Claus Jensen 14 Apr 2016, 10:35:03
Hey, getting this weird error. It's happening all of a sudden, and it sort of happened before, just the errormessage being MNTP: XPath error!. That sort of dissapeared by itself again. That turned out to be while our.umbraco.org had issues the other day. Made me think of som sort of call-home situation?
Today it turned out with the ucomponents error
If you please notice, it's the native mntp installed that gives the ucomponents error :-S
3 Attachments
Sorry, I set this to duplicate, but it turns out this is a different issue.
@Mads - can you please confirm which version of Umbraco and uComponents you are using?
Umbraco 4.11.1 ucomponents v. 5.3.0 (latest)
I've looked at the source for MNTP in both Umbraco core and uComponents.
The error message "{{uComponents: XPath Error!}}" should only appear when using the uComponents version. The native Umbraco core MNTP has the error message "{{umbraco.editorControls: MNTP: XPath Error!}}".
So I'm finding it confusing that the native version would be displaying the uComponents error message.
Following the logic from the source-code, the only reason that error message should appear is when the "XPath filter" contains an invalid XPath expression. (Which itself is referenced in another issue U4-1585)
@Mads - my super-quick-fix advice would be to delete the {{uComponents.Legacy.dll}} from your /bin folder. This would rule out any dependency on the legacy version of MNTP.
Just a thought, could it be some sort of error in the umbraco.config?
heh, just gave another error, the same as i've seen before :-S
@Mads - Okay, so that rules uComponents out, as the correct error message is being displayed. (Still find it strange that it was being displayed - will investigate further on that).
You could try refreshing the XML cache ({{umbraco.config}}), see if that makes a difference.
Otherwise, try re-saving the MNTP's prevalue-editor options?
Now i've tried deleting the ClientDependency files, republishing entire site, re-saving the MNTP AND touched webconf, still no fix!
It's probably some cookie stuff, that held me into the issue, until further notice it might be solved??? After i recycled the app pool it worked, so still som unstability here somewhere!
Priority: Normal
Type: Bug
State: Closed
Assignee:
Difficulty: Normal
Category:
Backwards Compatible: True
Fix Submitted:
Affected versions:
Due in version:
Sprint:
Story Points:
Cycle: