@Howdy_McGee An elected moderator is highlighted in bold ;)

@MarkKaplun it seems PHP < 7.0 will give you fatal error, if you create method name with reserved words. For example public function include(){} throws fatal error. PHP expects string after include keyword. lesson learned

How much attention do you need? My eyes are hurting!

it seems specific to SiteGround's cache system, but who knows. I'd wait for 4.6.1

Cheers. I tend to wait for the ..1 release normally regardless.

Okay so story time.

Client wanted me to make their top-bar and some banners sticky at the top + some other adjustments. One day job. Once finished, client asked their money back because apparently all of this could have been adjusted using the default theme preferences.

it’s no problem, as long as they return day’s worth of work back :)

I've worked with over 10 client the past week and a majority of them use Avada.

Didn't even know about this theme prior to this job. :)

reads avada - remembers it is one of those themeforest monster-themes - runs away screaming

it’s pretty much a parallel universe between conventional development and just buying off the shelf super–configurable stuff

I swear I loaded up a wp-admin page yesterday that pretty much crashed the entire server.

@Rarst Where "super–configurable" usually translates to super-bloated and confusing

well, duh, trade–offs

no-go I'd say.

(Sorry, grumpy day...)

If i have a rotating disk in the x-y plane and i apply a force along the x-y plane in line with the center of mass of the disk , will the disk move along the direction of the force or along a different direction ? I am asking this in reference to the precession of a gyroscope. Thank you.

@shashank I don't think this is the room for it... :)

Oh, okay sorry.

@shashank Well, if you use wp_rotate_disk($args) with an array of three that should be working ;-)

I get the feeling tickets like this are defunct core.trac.wordpress.org/ticket/25669

I don't see any reason to use the WP AJAX api now that we have register_rest_route(...)

@TomJNowell is that collision safe?

you need to specify your own namespace

but there's nothing to prevent you using WP AJAX with a silly generic name as it is

@toscho Your answer to customizing the output of the previous_post_link how would I check if your on say the first blog? because it is still displaying previous link even though I'm on the first blog wordpress.stackexchange.com/a/118719/85776

The first blog post? What is it currently linking to, the oldest post?

I'm assuming you're using these links on a single blog post template.

Yeah it's a single blog post template and I customized the output following what @toscho put in the answer. Say you have 2 blogs and you're on the first one you click next and you go to the next one but you can click next on that one as well but obviously you're one the last one so you shouldn't be able to click next - basically I want to hide it

Looks like that post is outdated - there's not even a $post object being passed to the filter.

Notice: Trying to get property of non-object in /Applications/MAMP/htdocs/wp-e4k/wp-content/themes/e4k-theme/functions.php on line 118
Line 118: $url = get_permalink( $post->ID );

I think here's what you'll need to do...

Modify toschos original filter and use get_adjacent_post() passing in previous = true or previous = false based on the current_filter() conditional.

This will get you your post object. IF get_adjacent_post() returns NULL or FALSE or some empty() value, then you can return false to your filter and the link will disappear.

Erm, get_adjacent_post() - not link.

Thanks :D I'll look into it now - btw congratz on the moderation :)

Thanks!!