You’re right. It’s my fault. Happy coding!
I already had a work around on another pluigin but i think something like this benefits your users of your plugin.
You see, im being nice, youre taking it wrong way again!
You’re right. I’m doing the wrong thing again. My bad.
To everyone else,
It’s true that there is nothing in my documentation that warns you not to try to use a shortcode as a shortcode attribute, as yodunnit had done here. Granted, the documentation _does_ tell you what all the valid shortcode attributes are, and what their accepted values are/can be. And it provides examples of how to do certain types of things, including setting up a basic [fileup] shortcode.
yodunnit’s shortcode is about as basic as they come. His only issue was a fundamental WordPress shortcode formatting error.
In future endeavors, I will add a disclaimer that if you choose not to use the provided modal shortcode generator, and build your shortcodes manually, that a basic understanding of WordPress shortcode formatting (which I do explicate at the top of my documentation for each shortcode) is recommended.
This has been a great thread. I’m sad to see it go.
TTFN
OK lets get something very very clear.
Your Plugin CANNOT insert shortcodes from the fileaway button in the tinymice editor as previously discussed in another users thread. Also the buttons collapse and you have to do various clicking to make thewm show up!
It is outdated, fundamentally floored with the documentation you have provided.
You are not catering for the average user, some users here are novices. However i am new to wordpress NOT to coding. I usually code in C# something you are not probably familiar with Mr Stark!
Most plugins have a very clear documentation unlike this one. It hasnt been updated for over 2 years which is why users are having trouble with your shortcode generator.
Funndmentals in creating a plugin, is to be clear and to be updated. WordPress has a huge following, so to save yourself embarassment Mr Stark i suggest you either develop a new plugin with Proper Documentation or remove it. It works sort of 60% but is not comapatible with later wordpress versions as a whole. If you use Ajax, it needs to be compatible with most browsers not just the odd 1 or two.
Also it helps to Beta Test.
Hope that clarifies your answers Mr Stark.
So before you start attacking users you need to reflect on your goodself.
-
This reply was modified 8 years, 3 months ago by
yodunnit.
P.S. – yodunnit was trying to use the debug attribute in a fileup shortcode. This was not his problem (it would have just been ignored, since it’s not a recognized attribute of fileup), but it demonstrates that yodunnit was not actually looking at the provided fileup tutorial documentation, because debug is not an attribute listed under the recognized fileup attributes in my exhaustive documentation.
Yodunnit, there are some other plugins that create javascript errors rendering the shortcode generator unusable. That is not an issue with File Away, but with those other plugins. This has been a recurring problem for some users. I have even helped users identify those problem plugins, and have even helped them fix the javascript in those other plugins so that File Away’s shortcode generator could work.
But I see you’re back to ignorance-based personal attacks again. You don’t seem to be able to sustain yourself very long without them.
“Also othe buttons collapse and you have to do various clicking to make thewm show up!”
lol. That’s called field dependencies. It’s to prevent you from using attributes that are incompatible with one another. It’s built-in intelligence.
Enjoy the rest of your day!
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
My decision is to close the thread. That decision won’t change, but you can talk to me on Slack (under my username) if you need further clarification: https://wordpress.slack.com/messages