I have written a plugin that interfaces with a third-party mailing API. I have created a settings page for my plugin that includes two buttons:
a submit button created with submit_button() which saves the form
a "test settings" button that should use the current values from the form without sav...
@Darth_Vader @Gabriel Please remember to look closely when suggesting/approving edits - this suggested edit actually added part of the answer text into a code block: wordpress.stackexchange.com/review/suggested-edits/109843 (I've fixed it now)
anyone ever play with Bootstrap nav walker? I've spend an hour trying to figure out how to turn the child menu from a div to a list. I can't seem to find a Q&A on it, but I was able to turn <div class="dropdown-menu"> into <ul class="dropdown-menu">?
@Rarst Exactly. I wish there was a way mods could cast a close 'vote' rather than it always be a hammer, for this exact situation. There might be times you want to contribute to the community consensus rather than force it :)
@Darth_Vader Have a look at the link. Part of the answer made it into the first code block. Also there were still backticks in the indented code. Just a reminder to double check before submitting the suggested edit, that's all. :)
@Darth_Vader I'm not sure if you're being sarcastic or not, just in case you are, suggested edits should generally be pretty good and fix everything with a post, to avoid wasting reviewer time - more here meta.stackexchange.com/a/76284/317795
@TimMalone I dont need a link for what was a one time error. Maybe next time you should say, hey, just FYI it looks like your edit text went into the code block
I disagree with the article, I am not a car mechanic and still I own and drive a car. I can ride a train, bus, plane, taxi, in a better comfort (maybe) but I don't need any special mechanical knowledge to own an engine on four wheels in which I can get from place A to B
the question should probably be, when the car gets old, will there be any spare parts to be able to service it when needed
There is nothing wrong with 5.2 itself. Sure it has bugs and other things that got improvments over time, but it is unlikely 7.0 is perfect
and that's part of the issue. major resources are burnt for the sake of compatibility with obsolete versions of language and compatibility with actual stable suffers.
The problem is not so much that people do not need to know the technical details, but that the marketing machine tells them it is just so easy anything can be done in 5 min by anyone
then the race to the bottom follows and people with any understanding of how to develop software and sites just go away from the wordpress game
When I need a car mechanic, I don't usually just go to any random person claiming to be one. Obviously some people do but then there is the regulation that force them from time to time to get a competent one
I don't think you really even disagree with my article :) you still acknowledge that to drive a car you need at the minimum know how to drive and that mechanic needs to service the car... WP pretends that to self-host a site you don't need anything, it's all magiced away!
it's like someone selling cars, putting under advantages that you don't need to know how to drive and it will never break
Yes, but I think most people understand that. Even getting a domain name requires some technical understanding that there is such a thing and what it does. so it is not black and what or any other firm borders thing. The question is how much should site owners know.
Core is obviously not helpful by adding more magic with language selection and now automatic language packs, but it is actually the things that are not in the core which IMO are the main issue hiding the complexities - proper backup system, proper plugin/theme testing sandbox, minimal security "defender".
Once I followed one of @gmazzap test related comment and found out there is undocumented feature of PHP that lets you control the inclusion of php files. In theory this can be used to have a smartphone like permission system to reduce access of plugins and theme
Core just doesn't try to make the site owners secure and busy with justifying it instead of fixing the issues (user enamuration is the obvious and easieest one to fix)
totally horrible and non secure htaccess by default
anyone ever play with post_links with a conditional if it's the 1st page and only visible is previous_posts_link do X and if it's the last page that only shows next_posts_link do Y?
@Darth_Vader Thanks, I suspected as much =] . But more specifically, should the suggested edit be denied or accepted? It appears to be an improvement to the original, but on the other hand it's difficult to verify that the two users are one and the same, in which case the modifications could actually be detrimental.
I would suggest approving it. I think it's only 2 rep points or something minimal for a correct edit so unless they are consistently doing this it's more beneficial to us as user trying to answer the question than that user trying to gain rep by edits.
@Darth_Vader I am not sure that's along the lines of what you think but I vaguely remember doing stuff with hanging items. i.e. if last page only has 1 post then tail it onto a previous page.
@Howdy_McGee I agree, if the post is an improvement do not deny it
@bosco I would flag to inform a mod and then they can send a mod email to notify the user they aren't supposed to have duplicate accounts, request SE to merge them or run a few checks to see if they are actually the same user with two different accounts and go from there. several options exist but it's all up to what the WP.SE mods want to do.
@Rarst Im looking for page a way to write a conditional on page 1 so that I can style just for next_posts_link() and the same for the last page that only has ` previous_posts_link()` and my searching seems wrong as I'm not getting anything
@Howdy_McGee @Darth_Vader Grazie! I accepted the edit. I won't flag it as nothing appears particularly malicious, I'd argue too trivial for mod attention. But I left a comment with a link to the account merge FAQ.