- plugin can't change primary key
- small Bug in _main.php "href" in 1.8.6 version
#3 Jan 05, 2007 09:25
Tried it, didn't like it. Adding a "help true" to each setting made the ? link show up, but it went to $help_url#settingname instead of readme.html#settingname. I even tried doing $r = array( and return $r instead of return array( because one never knows what might be a significant piece of the puzzle. Not a biggie, of course. People can still get the readme and read it if they want.
Hey I'm doing the "simple turing test" as a plugin. So far it looks like the readme will be bigger than the actual plugin 8|
#4 Jan 05, 2007 09:53
Damn, I knew it was to easy :P
You can also specify a full url for help, so you could cheat ;)
You'll have to learn to be more concise with your readme :p
#5 Jan 05, 2007 10:33
Cool. Will give it a shot, but I've been "unzipping the distro" (if ya know -hic- what I mean) a bit so I'll try to focus on my "are you human" plugin THEN, after much rest, give this a go. Looks much better, but that could be cuz I'm always impressed with arrays that got fancy stuff in them. Especially when the array is sniggled inside another array that won't be called until another array is recognized by something that's probably an array. Of arrays.
COMPLETELY UNRELATED, PLEASE CHECK THIS CODE FOR ERRORS
#6 Jan 05, 2007 10:38
#7 Jan 05, 2007 11:11
Clearly the cap on method needs to include a call to refreezer the "sauce code" :lol:
Back on track: I think maybe I should wait to see if blueyed considers replacing the page as a bug or an expected feature. As things stand now IF he chooses to make the page in the manual be valid then my readme will open to the correct P tag. Ideally it would also open a popup to the identified tag, but for now I'll just leave well enough alone.
Though a rev 0.3 would look like I'm fixing stuff...
#8 Jan 06, 2007 00:02
I normally start my plugins with a wierd version number like 127.0.0.1(stable) so it makes me look like I've been working my balls off upgrading it for years :roll: