Don’t get me wrong–I really appreciate this. It’s great to be able to start out with a skeleton component.
That being said, it would be a better idea to name the component something else rather than “component”. Throughout all the files, we’re supposed to replace “component” with our own component name, however, there are instances such as the flag “current-component” that should not be renamed, creating confusion. Now we don’t know if we’re supposed to replace “component_id” or not.
It would have been better to name the thing “example”, or another word not currently used in the bp structure so we can see exactly see where the component name comes in.
I know the skeleton is created for us to learn the structure, I am just saying naming it “component” is confusing.
Also, the skeleton component does not work straight uploaded into the mu-plugins? It adds a nav menu options, but the screens do not work, nor the sub navs. Any ideas?
Point taken, I may rename the functions.
It will only work the trunk, it won’t work with beta 2.
Andy,
Thanks for all your hard work! We all appreciate it.
I am looking forward to the next release!
I’ve updated it to v1.1 with a better naming convention and added nonce security:
http://tr.im/bpskel1_1 (zip link)
In the file “bp-example.php” on line 209:
if ( $bp->current_example== $bp->example->slug ) {
should read:
if ( $bp->current_component== $bp->example->slug ) {
shouldn’t it?
yep it should. I’ll update it this weekend.
The bad things about search&replace, huh? Throughout my plugin, there are comments like “In this mypluginname, we will…”
