This example challenge seems different than the video.

Howdy! Sorry, what did you mean by two different elements?

Sorry, two different "names" is probably a better way to say. In the video example we were told to use "wptreehouse_badges_styles" as the function name and the first thing passed to wp_enqueue_style. In the quiz, I needed to use "my_plugin_styles" for the function name and "my_plugin_css" for the first thing passed to wp_enqueue_style.

Hi, if I'm understanding you correctly this is correct. The idea is to have slightly different names in the code challenges compared to what we code in the example project. The goal is to let you see what naming conventions change when you look at different code samples doing the same thing.

Is that what you were curious about? Why the code challenge functions and project file functions did not have the same name?

Multi-Post edit #2... sorry...

Edit: see next post.

I am also looking for more information on this. I believe I do understand Mr. Hogan's concern.

The issue is not that variable and function names change in challenges with respect to the lessons. The issue that I find confusing, and I think the OP does as well, is this:

In the lesson, when the code is written for the wptreehouse_badges_styles() function:

function wptreehouse_badges_styles() {

    wp_enqueue_style( 'wptreehouse_badges_styles', plugins_url( 'wptreehouse-badges/wptreehouse-badges.css' ) );

You can see that the name of the function is the same as the name passed as the first argument (the handle) in the wp_enqueue_style function within. In short, the name of the custom function and the name of the handle passed within it to wp_enqueue_style are the same.

However, in the code challenge, the function being written is named 'my_plugin_styles' and the handle being passed to wp_enqueue_style is 'my_plugin_css'... obviously not the same name as the containing function:

// Handle: my_plugin_css
// Plugin folder: my-plugin
// CSS file: my-plugin.css

function my_plugin_styles() {
wp_enqueue_style( 'my_plugin_css', plugins_url('my-plugin/my-plugin.css'));

}

As I'm new to much of this, I could only refer to the preceding lesson and try to use the information there to make an attempt at the code challenge. Naturally, my first go at it looked something like this:

function my_plugin_styles() {
wp_enqueue_style( 'my_plugin_styles', plugins_url('my-plugin/my-plugin.css'));
}

I tried various guesses at the proper formatting and whatnot and was unable to arrive at the correct code until I found this thread (which in my book, means I had to cheat to get it.)

But classroom ethics aside, I'd like to try and understand all of this. The truth is, it's the naming logic in the code challenge that makes more sense to me than in the lesson. How is it that we can pass a function's name to another function within itself? Doesn't that cause an infinitely regressing loop?

Obviously, it doesn't since the live plugin, at this stage in the course, is working. But if you can help me understand how this self-referencing matter works (or doesn't), I'd greatly appreciate it.

Hi,

The first parameter for the wp_enqueue_style is a unique handle and can be whatever you set. It is not dependent or connected to the name of the function in which is resides.

The only place we pass the function name is to the add_action hook that will eventually come after the function.

Hope this clears things up a bit?