Xen Factory
Register today to become a member! Once signed in, you'll be able to start purchasing our products, ask questions, request support and suggest new ideas!
Support Fixed XFA Forum Sales: Warning: InvalidArgumentException: Accessed unknown getter 'xfa_fss_allow_sales'
- Thread starter wolven
- Start date
-
- Tags
- forum sales
Not I would know.
I have a classic setup for test, staging and production.
test and staging contain the same Ad-ons. test has no error messages, staging the errors reported.
I can't see the differences and going to check all properties again.
Is there anything I should check particularily?
Knut
I have a classic setup for test, staging and production.
test and staging contain the same Ad-ons. test has no error messages, staging the errors reported.
I can't see the differences and going to check all properties again.
Is there anything I should check particularily?
Knut
I tried something.
I suspect the error has something to do with the imported forums. As I haven't it experienced in the develop board which doesn't contain actual ads.
So I stopped allowing sales in the imported sales forum, made a new one with no ads in it and created an ad. Now I have no warning received.
Therfore, question: Might it be possible that the import of a former by Forum Sales used forums with running ads in it causes this behavior?
I suspect the error has something to do with the imported forums. As I haven't it experienced in the develop board which doesn't contain actual ads.
So I stopped allowing sales in the imported sales forum, made a new one with no ads in it and created an ad. Now I have no warning received.
Therfore, question: Might it be possible that the import of a former by Forum Sales used forums with running ads in it causes this behavior?
Last edited:
Ok, To happy too early,
The template error has gone, the "access unknown getter 'xfa_fss_allow_sales' is still in the logs.
Weird, because it checks the forums for allow sales even when it has it clearly not allowed.
Question: The sales forums get special access rights. Might this forum based rights cause this conflict?
Edit:
I've checked the above by setting back all access rights to one of the imported forums -> no change
Interestingly, the new created sales forum produces the same error.
Now, I suspect that some options (or better the request of that options) create this error.
The template error has gone, the "access unknown getter 'xfa_fss_allow_sales' is still in the logs.
Weird, because it checks the forums for allow sales even when it has it clearly not allowed.
Question: The sales forums get special access rights. Might this forum based rights cause this conflict?
Edit:
I've checked the above by setting back all access rights to one of the imported forums -> no change
Interestingly, the new created sales forum produces the same error.
Now, I suspect that some options (or better the request of that options) create this error.
Last edited:
I tried again things but this leaves me even more puzzled.
I have all caches switched off.
I've checked all the widgets and can't see any difference to the dev-forum. I did suspect that a widget might cause this,
- Deactivated Forum Sales Add-on - Error gone, re-activated again: error there.
- Deactivated all other add ons except Core and Forum Sales: error there.
- Deinstall Core and Forum Sales, Checked Database and Files: All gone. So no error in log.
- Download Core 1.9.1 and Forum Sales 2.3.1 as zip file. Upload and fresh install! Error back again! All forums were disabled for sales, the error came up before putting any option.
I have all caches switched off.
I've checked all the widgets and can't see any difference to the dev-forum. I did suspect that a widget might cause this,
I found a solution which I do not understand.
Suspecting the widgets, I took off the homepage. After switching off, the error was gone.
Then, I took the home page on but commented all widgets at the home page off - just the title were on. It led to a empty home page with title. But: Same error!
Then I reverted the home page options from "element" to basic, changed in the main options the home page and the error disappeared. I took all widgets on home page step by step back and the error did not come back.
I have no idea why the way of linking the home page element at the navigation leads to this error. I have the setup running on the dev site without errors.
Now, after reverting and configuring as basic type, the error has gone.
I hope, you can explain to me what the cause might be.
For the time being, the problem seems to be solved.
Suspecting the widgets, I took off the homepage. After switching off, the error was gone.
Then, I took the home page on but commented all widgets at the home page off - just the title were on. It led to a empty home page with title. But: Same error!
Then I reverted the home page options from "element" to basic, changed in the main options the home page and the error disappeared. I took all widgets on home page step by step back and the error did not come back.
I have no idea why the way of linking the home page element at the navigation leads to this error. I have the setup running on the dev site without errors.
Now, after reverting and configuring as basic type, the error has gone.
I hope, you can explain to me what the cause might be.
For the time being, the problem seems to be solved.
It doesn't, but the permission can sell for a user go through all nodes.
What do you mean by "from element to basic" ?