I appreciate the reply.
I know its suppose to be straight foward. I dont know if I am the only that has the problem. But its easily replicated.
I create a sidebar -it stores as post type ‘sidebar’.
Now when I try edit that sidebar and try save again it now saves as post type ‘page’. If you are not able to replicate it then we’ll just say its a conflict with one of my own plugins then.
Let me paint you my scenario. My template will be using taxonomies that could consist of over 20,000 terms. Are you suggesting that (for example) If I wanted to load an image on a sidebar per term basis – the best way would be to have 20,000 image widgets on the main admin widget screen?? Or perhaps use a dynamic image widget?? I feel that shouldn’t have to be the case.
I played with your widget for 2 nights, scratching my head to get it to work properly with my template, whilst also trying to picture how the potential 20,000 + taxonomy term database aspect of my problem could be addressed with it.
i figured i was the only having these concerns with the plugin so i moved on.
Alot of people probably don’t notice, but the Per Page Widget plugin not only lets u assign widget per Page, but it works with any taxonomy; word-press-default, custom, public or private. Alongside with Widget Logic, there’s really nothing you cant accomplish.
If your widget can accomplish what these two can + a way to accommodate the defining of sidebars for over 20,000+ terms in the Admin backend without having to use dynamic widgets or cluster up the sidebar with widgets then i’m all game to find out why its conflicting with my template if you have the time that is.
Thanks for your time.