- This topic has 14 replies, 2 voices, and was last updated 14 years, 9 months ago by
.
-
Posts
-
First off hello, im brandon!
I am having some issues with the menu creator
I can not figure out for the life of me how to use the plugin. I can create a single drop down with pages, but i want to have multiple drop downs with different pages in each one.
Here is what im trying to do basically:
http://grab.by/2tbbTop layer links when clicked will just go to the first page in each list.
(eg: if you click family, it will go to the family galleries page)If to acheive this i have to use the custom tab then i can consolidate the "journal" tab and use the pages tab for the "about" link. And if custom drop down is my solution were can i find a example template on how to code it???
every link on here will link to a static WP page.
It seems like it should be simple but i CANNOT figure it out!
Hi,
This is a common question I am asked, so instead of replying to you here in the forum I’ve written a help page which partially answers you question.https://geek.hellyer.kiwi/help/pixopoint-menu-items/
The "Single dropdown" checkbox is what you need to change to show all of your pages.
I’ll be slowly adding to that page as I find the time. Your question just motivated me to start that particular page
” title=”Smiley” />ah! this didn’t help at all
Sorry to bother you again, but i think the thing im confused about is how to format the custom code tabs. That is IF the custom tabs are my solution. I searched the forum for about an hour and a half looking for a custom tab example, you mentioned it to someone who had a similar question, and told him you would format it for him for 5$ but i couldn’t find the example anywhere!
I have 5 years of html experience not writing it but working with code and 3 years of modifying and making WP themes so im surprised i cant figure this out.
Sorry, from your post I assumed you were just using the Custom code option as a way to get around the issue of only a single dropdown with your pages in it.
The Custom Code allows you to add HTML.
Here’s another article which will hopefully help:
https://geek.hellyer.kiwi/help/pixopoint-menu-custom-code/I’m wondering now if it might be a good idea for me to include some custom HTML in the default installation so that people like yourself can see how it works.
Yea! Including custom code examples would probably help a lot
” title=”Wink” /> alright so i added it and nothing seems to be showing up. I havent modified the code from the example and i havent modified the plugin… Weird ill keep trying and get back to you.Ok i figured it out! I had to downgrade a version. To the version on the WP plugin site! So i read multiple threads were you said that you still havent seen a menu that needs more then 4 custom code buttons?
” title=”Cheesy” />this one needs 6! although im just going to get rid of the journal drop down and go to galleries when you click it. This brings me to my next point. How do i set up the menu like this?
pages(home, about) custom(weddings) custom2(realkids) custom3(seniors) custom4(family) pages(journal, blog, reviews, contact)
How do i add more then one pages button?
SCRATCH THAT! I just relized i can create 2 tabs with ONE custom code tab, i dont think people relize this and thats why they want more then 4 custom tabs!!!
"akeyo" wrote:… i dont think people relize this and thats why they want more then 4 custom tabs!!!Yep. I’ve tried writing out an explanation for that, but I find it always comes across as condescending
” title=”Sad” />"akeyo" wrote:How do i add more then one pages button?You can’t. I may add support for that in a future release though or as an extension plugin.
"akeyo" wrote:Ok i figured it out! I had to downgrade a version. To the version on the WP plugin site!Were you using the beta plugin from here? … https://geek.hellyer.kiwi/pixopoint-menu-plugin-beta-0-8/
If it was, then could you let me know what HTML you were using? I placed a bunch of security systems in place. One of those security systems is probably blocking the plugin from working but I’m not sure what.
I think I found the problem
” title=”Smiley” /> I tried to edit my own menu and discovered it wasn’t working! (I use the latest beta)Yes it was the latest build, and i tried the code straight from the example page. Also, like i said i dont write code but i can read it and modify it no problem. Like i can say i want to make this change and find that code and modify it all i want. But when i try and write it, i have a hard time. So me being used to getting things working i just downgraded and had NO problem now its SUPER easy. And i got the menu up and working in under 5 minutes. I have just one tab, the custom code 1 and have like 10 tabs on my main site.
This plugin helped SO much and was so easy once i figured it out. I defiantly would include some sample code because i searched the forums for at least 2 hours and looked through all the blog posts unless i overlooked it i couldn’t find that page you linked me to ANYWHERE i think the best thing you could do would be write a small getting started tutorial explaining the functions of the different options, and explaining how to set up a custom tab.
Thanks so much for the plugin and the support. You were fast and extremely helpful and very kind! Its always nice to see a free plugin with good free support, i would buy the premium support to help you out. But im doing this site for a friend for free, so it would be coming out of my non existent budget
” title=”Wink” />The bug in the beta has now been fixed … https://geek.hellyer.kiwi/pixopoint-menu-plugin-beta-0-8/
It was triggered by using the include/exclude pages/categories and/or the page URL excluder. If you didn’t use any of those, it should have worked fine. I’m using them on PixoPoint.com hence it borked itself quite badly when I went to re-edit them. When I set the menu up here I would have removed all of the security settings and once I had the security settings corrected I re-uploaded. I guess I never tested it locally with the options which caused it to glitch hence I didn’t notice it. Sorry for the bug (which is now fixed)!
- You must be logged in to reply to this topic.