Icy Phoenix

I ran in to a small issue. Me being me, I have to click links of all sorts in places most people would never click, but if it there, I'm going to click it just because. If it don't work it needs fixed or gone so there for I test and test and click and click.

In the Knowledge Base there is a link and here it is:



Clicking that gave me this:



In this case I know for 100% certain it is a php.ini error. BUT for all you coding gurus out there, is there any way to fix this on a server that we do NOT have access to the php.ini file? Obviously you can tell from the screnshot this error is on my local host server so iw as able to fix it by setting:

Can I drop this: in my code somewhere and make it work on my live web host?

To be exact I think it is a not a regular php.ini issue

Anyway, this problem should never be an issue on my site for any user at any time other than a mod or admin. Normal users will never see that link..... I think. that was in my forum that I have it set to view Private. So if no fix, that's perfectly fine by me. was just food for thought.

I don't think it's a ini error. It seems it doesn't know when to stop going forward. I'll look after I'm done with the github tickets

did you, by any "luck", put a category as a parent of itself?

Informpro wrote: [View Post]

did you, by any "luck", put a category as a parent of itself?

I'm 100% for certain that was not the case. I went back and tried again with the same exact results.

Okay, I'm starting to get an idea. Can you tell me how many categories you had then?

My setup is as follows.

Categories and types = 4

Forums for comments to go to = 4

All 4 forums set up as KB Mode in forum setting when setting up that forum.


The first image in my original post all the way up top, you can see the link I clicked to get the error. That was in the forum where the KB category sends its comments to, NOT in the KB.

The forums are setup to view as private so no one but mods and admin can see the forums so registered members MUST use the KB instead or they will just short cut right to the forums instead. So when you set up the forum for comments, make sure to set it to view private and make it so the forum is in KB Mode.

Now go to your Knowledge Base and choose any category you wish. Submit a new article. Now make a comment on said article. Now at this point in time, users would be redirected the forums to submit and view comments. You as an admin can just go to your forums and click on that private forum where the comment just went and read the article heading. Click that link that says read complete story. Now enjoy the error.

If my instructions are confusing (they so often are) I can break out the old recording studio and do a quick youtube video.

That should be enough. I just need to reduce my local config to reproduce it; no big deal.

Yeah its really no biggie man. I had to dig deep to find this one. The realistic odds of the regular Joe running in to this issue is slim to none really. I just managed to get "lucky" if that is what you wish to call it and find it.

Just to check something – are you using the "Forum KB" feature in Forum Management, or the KB plugin? Both are unrelated.

EDIT: in the meantime i fixed a bug and 2 weird things in KB! Hopefully MG will be able to look at it soon enough.

First off, sorry so slow on the reply. I have been plagued with internet outage the last week. Sporadic service at best.

And good catch. I do have KB Feature turned on for the forums where the KB plugin comments go.

I will go turn that feature off right now and test. I will come back and post.

**UPDATE**

I shut off KB Mode for the forums where the KB Plugin comments go and that error is gone. If I click the read full article link now, it displays the whole article and not an error.

I will have a look at this as soon as I have some free time... it's a busy period...

Informpro wrote: [View Post]

EDIT: in the meantime i fixed a bug and 2 weird things in KB! Hopefully MG will be able to look at it soon enough.

Hmm fixes on Git? I'm curious as usual.

Yup! I think they were merged on the plugins repo

Nice! Ill have a look as soon as my I get my PC reformatted tonight.

I never got to go check out the fixes. I am on my way now.

P.S. I love having time again to work on my icy projects.

Hey Ray, do you remember if you ended up figuring out what caused the bug?

Nope. Not at all. This one has been a good bit back. Suffering major PTSD since then with memory loss. I do know that when you brought up the forum KB management setting or whatever it was, when I turned that off, that link error went away. When I turned it back on, it came back.

I actually have no installs at the moment. I did try to install one here a week or two ago I think it was and it was a complete miserable failure for some reason. I'll try again and see if I can replicate this and why or how.


**EDIT**

Today is 1/02/2019 and I had a chance to revisit this. I reinstalled a fresh IP and made sure everything was running as silky smooth as it possibly could. I then reinstalled the KB and no errors at all. The only way at all I could get this error to replicate was to tick the box in the forum for the KB to make the forum post read like a KB article comments (KB Mode).

The only way that error went away without unticking that KB Mode in the forum setting was to alter the phpini xdebug on my server. I can 100% confirm the error went away when I added the xdebug nested 200 line to my phpini file AND left the KB Mode on in the forum settings.

As I stated though in my previous post, a user will never see this error. Only an Admin or mod will. It still is not pretty and shouldn't be seen but, it is what it is. Alter the ini file or don't use Kb Mode or deal with a big long error. As for the proper code to fix it, well, that is out of my area of expertise. I looked and nothing slapped me in the face as expected it wouldn't.


Now all that aside, would a user really use KB Mode for a forum thread that is a KB comments thread anyhow? I mean I did but I test. That is what I do. But realistically. But none the less, that error went on and on and on. Glad I figured a small part of it out. If you need any screen shots of my ini file or my Icy setup or my server specs, by all means please do let me know. I'll be glad to share info.

Ray, are you able to reproduce this on your local install(s) ATM? I'm still unable to.

Oops, just noticed that the kb_rate page had the header/footer twice...

I'll give ti a test install again and try. I should be able to if I can retrace my steps and reproduce exactly what happened.