XF 2.2 Error setting node permissions

[Geni]

Recent import from VB4. Still closed for testing so no hurry to fix this, but would appreciate any help.

When I try to edit node permissions I get the followoing:

An exception occurred: [InvalidArgumentException] Class XF\Permission\NodeList does not match formatter pattern %s\%s\View\%s in src/XF.php on line 1129

1. XF::stringToClass() in src/XF/App.php at line 1667
2. XF\App->XF\{closure}() in src/XF/Container.php at line 234
3. XF\Container->create() in src/XF/Container.php at line 247
4. XF\Container->XF\{closure}() in src/XF/Mvc/Renderer/AbstractRenderer.php at line 79
5. XF\Mvc\Renderer\AbstractRenderer->createViewObject() in src/XF/Mvc/Renderer/AbstractRenderer.php at line 87
6. XF\Mvc\Renderer\AbstractRenderer->renderViewObject() in src/XF/Mvc/Renderer/Html.php at line 47
7. XF\Mvc\Renderer\Html->renderView() in src/XF/Mvc/Dispatcher.php at line 460
8. XF\Mvc\Dispatcher->renderView() in src/XF/Mvc/Dispatcher.php at line 442
9. XF\Mvc\Dispatcher->renderReply() in src/XF/Mvc/Dispatcher.php at line 402
10. XF\Mvc\Dispatcher->render() in src/XF/Mvc/Dispatcher.php at line 60
11. XF\Mvc\Dispatcher->run() in src/XF/App.php at line 2485
12. XF\App->run() in src/XF.php at line 524
13. XF::runApp() in admin.php at line 13

Everything else works fine. Latest XF + Media Gallery. I have tried disabling Modsecurity to test but makes no difference.

If anybody could point me in the right direction, that would be great. Ultimately I will try another instance as I'm almost certain this worked a couple of days ago when I first installed it.

 

[Paul B]

A fixed released was issued yesterday to resolve that.

Upgrading to the latest version will fix it.

 

[Geni]

Oh great!

I just love it when its not my fault

Thanks.

Oh, If you mean 2.2.16 I already upgraded yesterday.






Perhaps downloading this version as an upgrade and doing it the old fashioned way...

 

[Geni]

Downloaded 2.2.16 patch-1 and did the upgrade that way. Apparently the patched 2.2.16 was not being propagated through the internal upgrade system yet.

Everything works now. Thanks Paul B. It was quick and painless.

 

[ChadCLund]

I have the same issue on a xenForo hosted forum. I upgraded yesterday (XenForo Cloud 2.2.16), but not sure where to find the patch

 

[Paul B]

If you are running XenForo Cloud, the fixes have been applied automatically.

I have also replied to your ticket with regards to this.

 

[ChadCLund]

ok, so here is NOT what I am understanding...

I use xenForo cloud because I am NOT a php developer. I pay the $60 per month so that I do not have to worry about these things.
I understand that coding errors happen (I am a .NET developer).
I understand that a patch was released that SPECIFICALLY addressed this error.
I understand that as a XF Cloud customer, these patches are automatically applied to my code base (assuming I am upgraded to the latest version which I did on Thursday.
HOWEVER, this morning, after disabling all of my add-ons (again), and even deleting some that were no longer needed, the problem still exists.
I am NOT trying to be difficult, or a ****. I just want this error fixed, so I do not lose my client.
As it stands now, I cannot edit permissions on any node, and my clients members are currently blocked from viewing these nodes. It is having a major negative effect on business, which I now am receiving the brunt of the complaints.

Please do what you have to do to fix this issue. It is NOT the add-ons. The latest patch (if actually applied), did not fix it.
Once again, I pay extra for the xf cloud version to avoid having these issues, as I am not qualified to address them.

 

[ChadCLund]

ok, so here is NOT what I am understanding...

I use xenForo cloud because I am NOT a php developer. I pay the $60 per month so that I do not have to worry about these things.
I understand that coding errors happen (I am a .NET developer).
I understand that a patch was released that SPECIFICALLY addressed this error.
I understand that as a XF Cloud customer, these patches are automatically applied to my code base (assuming I am upgraded to the latest version which I did on Thursday.
HOWEVER, this morning, after disabling all of my add-ons (again), and even deleting some that were no longer needed, the problem still exists.
I am NOT trying to be difficult, or a d1ck. I just want this error fixed, so I do not lose my client.
As it stands now, I cannot edit permissions on any node, and my clients members are currently blocked from viewing these nodes. It is having a major negative effect on business, which I now am receiving the brunt of the complaints.

Please do what you have to do to fix this issue. It is NOT the add-ons. The latest patch (if actually applied), did not fix it.
Once again, I pay extra for the xf cloud version to avoid having these issues, as I am not qualified to address them.

OK, they just fixed it. Thank you.
I may complain, but I also give credit where credit is due. Thank you for addressing this. I will advise my client.

 

[Paul B]

To clarify the specific issue, the patch was rolled out on Cloud to installs running 2.2.15 but we omitted to roll it out for installs running 2.2.16.

This was an error on our part.

 

[Kevin RG]

To clarify the specific issue, the patch was rolled out on Cloud to installs running 2.2.15 but we omitted to roll it out for installs running 2.2.16.

This was an error on our part.

Hi Paul,

I have the same problem, i have update my board to 2.2.16 patch 2 and the error remains.

does not match formatter pattern %s\Finder\%s in src/XF.php at line 1129

Do you have an idea to resolve this please ?

Thanks,
Br

 

[Jeremy P]

You would have to post the full stack trace to determine where the error actually lies.

 

[Kevin RG]

You would have to post the full stack trace to determine where the error actually lies.

Hi Jeremy,

I have found the problem, is not a problem of XenForo, it's an mistake inside an addon :
Wrong declaration of the entity location

• Before : \Addon\Entity\Class
• After: Addon:Class

And with this modification the problem is resolve.

Sorry for the inconvenience,
Br