Unable to add more menu items
AnonymousJuly 28, 2014 at 5:44 am #9217
I have a whopper of a menu, currently I’m at 86 categories. I can add four more before it tops out, but that’s not going to be enough.
I’ve done quite a bit of research and it appears that some people max out at 14, others at 48 and others at 90. Seems I’m one of the latter. The solution I found was to contact my ISP and request that they add this to the PHP.ini file:
suhosin.post.max_vars = 5000
suhosin.request.max_vars = 5000
They were happy enough to do that and it was taken care of through live chat. Unforthuately it doesn’t seem to have made any difference. The menu still tops out at 90 categories.
Wondering if anyone might have some suggestions or other avenues I could try. Only thing I can think of is to break the menus up into two, but I’d prefer to do that only as a last resort….
Thanks for any help.
AnonymousJuly 30, 2014 at 4:48 am #43033
I’m not sure if they did that but, in any case, I checked today and was still unable to add further items to the menu. I contacted Host Gator again and they tried to fix it for me, all to no avail. The latest from them is that a plugin may be interferring with the WP Menu Function.
Host Gator did create a ticket for me and they’ll look into it from their end. I’ll post an update with their findings, just in case it helps someone else in the future.
Anyhow, this is obviously not a Graphene related issue, so I’ll close this thread off for now. Sorry about that, it was a case of not knowing what I didn’t know…..
Thanks for getting back to me Ken. As always, your help is appreciated.
AnonymousJuly 30, 2014 at 11:36 pm #43034
As it turns out, it wasn’t a plugin conflict at all.
If anyone stumbles across this thread because you’re experiencing the same problem, just get your host to check that the PHP.ini file is updating and loading. For some reason, mine was not but it’s been fixed now and the menu function is working as it should….Mod
AnonymousAugust 3, 2014 at 1:07 am #43036
Hmmm, I’m on shared hosting so I guess maybe this was something that needed to be handled by the host…..
You must be logged in to reply to this topic.