1429
Quote:
Catzwolf wrote:
@Bender:
What you are implying here is pretty serious. I can assure you that this is NOTHING to do with WF-Sections and I am 100% sure of that.
Please i hope you take no offense in my post.
It was not my intention to accuse you or your great module of anything. Thats why i put the red line above it and went into a pretty much detailed description.
If you or anyone else for that matter are offended by my post i offer an excuse to anyone who is. I´m serious about this.
Quote:
WF-Sections does NOT overwrite any other file, either within its own directory nor does it to any XOOPS files.
Thought so, but didn´t know for sure.
Quote:
As for server error 500, it maybe possible, but I have never come across this with this module for a long time. A previous unreleased version ...
Well as this does actually happen on basic XOOPS files already it won´t be wf-section obviously.
Quote:
If you want me to install WF-Sections on one of your websites and test it out, then I would be only to glad to and this way, if it is WF-Sections then I can improve the script but I am more than confident that your problem lies else where.
Thanks for the offer but for now you have enough to do polishing and finishing this great module anyway.
So don´t you waste time on installations for others in uncertain cases like this. I will try to find the reason on my own for now.
Still everyone else who might have any advise for me as to what to look for is very welcome. As this is most likely not a wf-section caused problem please PM / email me so we can keep this thread to wf-section.