I am going to show you all of this tutorial using the page-theme method because it is probably the easiest to implement for beginners. This will also give you an intro into page themes, if your not familiar with it.
\nTo start our theme, you will need to do the following:
\n- \n
- Install WordPress \n
- Navigate to your wp-content/themes folder and choose a theme to edit or install a new one \n
- create a file called page-login.php in the theme directory \n
- Next open that file with a text editor of your choosing and add the following at the top of the php file. \n
<?php\n/*\nTemplate Name: Login\n*/\n \nget_header(); ?>\n \n<div id="primary" class="content-area">\n<div id="content" class="site-content" role="main">\n \n</div><!-- #content -->\n</div><!-- #primary -->\n \n<?php get_sidebar(); ?>\n<?php get_footer(); ?>To initialize this page template, make sure to activate the theme you've selected in \"Appearance/Themes\" in your admin dashboard and then navigate to a page or post. On the right hand side of your page/post editor you should now see a dropdown available for template under \"Page Attributes\". Change your template to \"Login\" or to the name that you specified in \"Template Name:\" and that will attach that page theme to this page/post.
\nNow we're ready to start editing this page-login.php template file. So first open this file in your favorite editor and Let's get a login page started.
\nTo quickly show you how to get this login on the page Let's paste the following code between the div with id of content.
\n<div id="primary" class="content-area">\n<div id="content" class="site-content" role="main">\n<?php wp_login_form(); ?>\n</div><!-- #content -->\n</div><!-- #primary -->Look at what that small piece of code do
\nNow we need to set some arguments that we can provide to this form to customize it. Let's take a look at the documentation for wploginform()
\nIn that document, it explains all the uses and arguments of wploginform(). Let's use those arguments section and see what happens. Paste the $args section shown in the wordpress doc right above our login form.
\n<?php $args = array(\n'echo' => true,\n'redirect' => ( is_ssl() ? 'https://' : 'http://' ) . $_SERVER['HTTP_HOST'] . $_SERVER['REQUEST_URI'],\n'form_id' => 'loginform',\n'label_username' => __( 'Username' ),\n'label_password' => __( 'Password' ),\n'label_remember' => __( 'Remember Me' ),\n'label_log_in' => __( 'Log In' ),\n'id_username' => 'user_login',\n'id_password' => 'user_pass',\n'id_remember' => 'rememberme',\n'id_submit' => 'wp-submit',\n'remember' => true,\n'value_username' => '',\n'value_remember' => false\n); ?>\n<?php wp_login_form( $args ); ?>It will look the same as the one we did earlier but, by customizing the arguments above, you can customize elements of the login form.
\nHandling the login form response (Custom)
\nTo handle the Login Form response we need to grab the $_POST parameters and login the user. You can create this as complex as you like, but I will demonstrate a simpler but effective method.
\nFor this action, we'll be using the aftersetuptheme and wp_authenticate. I have added the following two functions within the functions.php file. The first function optionalemailaddress_login searches for a users email address based on their username, with this functionality you can log in using your email address or the username.
\nThe second function, login_user, handles the actual functionality of the login by receiving the $POST parameters and passing them into the wpsignon method.
\n/**\n* optional_email_address_login allows the user\n* to log in with a email address as well as a username\n* @param string &$username username or email\n* @param string &$password password\n*/\nfunction optional_email_address_login( &$username, &$password ) {\n$user = get_user_by( 'email', $username );\nif ( ! empty( $user->user_login ) )\n{\n$username = $user->user_login;\n}\n}\n// Allows the use of email logins\nadd_action( 'wp_authenticate', 'optional_email_address_login', 1, 2 );\n \n/**\n* login_user handles the $_POST array and logs in users\n*/\nfunction login_user() {\nif ( ! is_user_logged_in() ) {\n$creds = array();\n$creds['user_login'] = isset( $_POST['log'] ) ? $_POST['log'] : '';\n$creds['user_password'] = isset( $_POST['pwd'] ) ? $_POST['pwd'] : '';\n$creds['remember'] = isset( $_POST['rememberme'] ) ? true : false;\n$user = wp_signon( $creds, false );\n \nif ( is_wp_error( $user ) ) {\nerror_log( $user->get_error_message() );\n}\n}\n}\n// Run login_user before headers and cookies are sent\nadd_action( 'after_setup_theme', 'login_user' );In this example I have used the default WordPress login form that you could customize and style to your desire. In the next blog, I will be demonstrating how to build a login form that is fully customized. We won’t be using the provided wordpress functions!
\n","frontmatter":{"date":"March 01, 2016","updated_date":null,"description":null,"title":"Wordpress Custom Login Form Part 1","tags":["WordPress","Learning"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1,"src":"/static/400bee4b6d2f5f571912dff23f863421/6d161/wordpress-icon-150x1501-150x150.png","srcSet":"/static/400bee4b6d2f5f571912dff23f863421/6d161/wordpress-icon-150x1501-150x150.png 150w","sizes":"(max-width: 150px) 100vw, 150px"}}},"author":{"id":"Zoie Carnegie","github":null,"avatar":null}}}},{"node":{"excerpt":"1. Secure your server Many known attacks are possible only once physically accessing a machine. For this reason, it is best to have the…","fields":{"slug":"/engineering/is-your-database-secured-think-again/"},"html":"1. Secure your server
\nMany known attacks are possible only once physically accessing a machine. For this reason, it is best to have the application server and the database server on different machines. If this is not possible, greater care must be taken, Otherwise, by executing remote commands via an application server, an attacker may be able to harm your database even without permissions. For this reason, any service running on the same machine as the database should be granted the lowest possible permission that still allows the service to operate.
\n2. Localhost Security or Disable or restrict remote access Consider whether MySQL will be retrieved from the system or directly accessed from its own server. On the off chance that remote access is utilized, guarantee that just characterized hosts can get to the server. This is commonly done through TCP wrappers, IP tables, or some other firewall programming or hardware accessibility tools. skip-networking The document is situated in the \"C:\\Program Files\\MySQL\\MySQL Server 5.1\" catalog on the Windows operating system or \"/etc/my.cnf\" or \"/etc/mysql/my.cnf\" on Linux. Another possible solution is to force MySQL to listen only to the localhost by adding the following line in the [mysqld] section of my.cnfbind-address=127.0.0.1 3. Disable the use of LOCAL INFILE The next change is to disable the use of the \"LOAD DATA LOCAL INFILE\" command, which will help to keep unapproved perusing from neighborhood records. This is particularly vital when new SQL Injection vulnerabilities in PHP applications are found. Or even significantly less difficult: To disable the usage of the \"LOCAL INFILE\" command, the following parameter should be added in the [mysqld] section of the MySQL configuration file. 4. Change root username and password, keep them strong. The default administrator username on the MySQL server is \"root\". Hackers often attempt to gain access to its permissions. To make this task harder, rename \"root\" to something else and provide it with a long, complex alphanumeric password. To rename the administrator’s username, use the rename command in the MySQL console: The MySQL \"RENAME USER\" command first appeared in MySQL version 5.0.2. If you use an older version of MySQL, you can use other commands to rename a user: To change a user’s password, use the following command-line command: It is also possible to change the password using the \"mysqladmin\" utility: 5. Remove the \"Test\" database MySQL comes with a \"test\" database intended as a test space. It can be accessed by the anonymous user, and is therefore used by numerous attacks. Or use the \"mysqladmin\" command: 6. Remove Anonymous and outdated accounts The MySQL database comes with some anonymous users with blank passwords. As a result, anyone can connect to the database to check whether this is the case, do the following: In a secure system, no lines should be echoed back. Another way to do the same: If the grants exist, then anybody can access the database and at least use the default database\"test\". Check this with: To remove the account, execute the following command: The MySQL \"DROP USER\" command is supported starting with MySQL version 5.0. If you use an older version of MySQL, you can remove the account as follows: 7. Increase security with Role Based Access Control A very common database security recommendation is to lower the permissions given to various parties. MySQL is no different. Typically, when developers work, they use the system's maximum permission and give less consideration to permission principles than we might expect. This practice can expose the database to significant risk. In addition, ensure that only the user \"mysql\" and \"root\" have access to the directory 8. Keep a check on database privileges Operating system permissions were fixed in the preceding section. Now let’s talk about database permissions. In most cases, there is an administrator user (the renamed \"root\") and one or more actual users who coexist in the database. Usually, the \"root\" has nothing to do with the data in the database; instead, it is used to maintain the server and its tables, to give and revoke permissions, etc. Only administrator accounts needs to be granted the SUPER / PROCESS /FILE privileges and access to the mysql database. Usually, it is a good idea to lower the administrator’s permissions for accessing the data. Review the privileges of the rest of the users and ensure that these are set appropriately. This can be done using the following steps. [Identify users] [List grants of all users] The above statement has to be executed for each user ! Note that only users who really need root privileges should be granted them. Another interesting privilege is \"SHOW DATABASES\". By default, the command can be used by everyone having access to the MySQL prompt. They can use it to gather information (e.g., getting database names) before attacking the database by, for instance, stealing the data. To prevent this, it is recommended that you follow the procedures described below. To disable the usage of the \"SHOW DATABASES\" command, the following parameter should be added in the [mysqld] section of the [mysqld] 9. Enable Logging If your database server does not execute many queries, it is recommended that you enable transaction logging, by adding the following line to [mysqld] section of the [mysqld] This is not recommended for heavy production MySQL servers because it causes high overhead on the server. Error logEnsure only \"root\" and \"mysql\" have access to the log file \"hostname.err\". The file is stored in the mysql data directory. This file contains very sensitive information such as passwords, addresses, table names, stored procedure names and code parts. It can be used for information gathering, and in some cases, can provide the attacker with the information needed to exploit the database, the machine on which the database is installed, or the data inside it. MySQL logEnsure only \"root\" and \"mysql\" have access to the logfile \"logfile XY\". The file is stored in the mysql data directory. 10. Change the root directory A chroot on UNIX {operating system} operating systems is an operation that changes the apparent disk root directory for the present running method and its children. A program that's re-rooted to a different directory cannot access or name files outside that directory, and therefore the directory is named a \"chroot jail\" or (less commonly) a \"chroot prison\". By using the chroot environment, the write access of the mySQL processes (and child processes) can be limited, increasing the security of the server. Ensure that a dedicated directory exists for the chrooted environment. This should be something like: [client] Thanks to that line of code, there will be no need to supply the mysql, mysqladmin, mysqldump etc. commands with the 11. Delete old logs regularly During the installation procedures, there's plenty of sensitive data which will assist unwelcome users to assault a database. This data is kept within the server’s history and might be terribly useful if one thing goes wrong during the installation. By analyzing the history files, administrators can figure out what has gone wrong and probably fix things up. However, these files are not needed after installation is complete. In conclusion,we should emphasize on database security. However it should be the first thing for any individual or a company. Manipulating collections like arrays and objects can be a hassle with vanilla JS. Thankfully there are libraries like Underscore which offer some extremely useful low level utility functions. Underscore JS provides much of the array/collection/object manipulating functionality similar to what you may have seen in other languages such as Ruby. As for calling the methods if you're familiar with JQuery, Underscore is identical except instead of \"$\" we use the library's namesake \"_\" to access the methods. Underscore has over 100 functions that can be used on collections, arrays, objects and functions (you read that right, function functions). I'm going to be discussing a few of the functions that work on collections, but definitely check out what else Underscore has to offer. Once you know how to re-create the same output with Underscore syntax, you'll never want to go back to plain old JS and using nested for loops. One of the most helpful tools Underscore provides for accomplishing this is... The _each method does exactly what it sounds like. It works on collections (arrays or objects), and will iterate over each element in the collection invoking the function you specified with 3 arguments (value, index, list) with index being replaced by key if used on an object. It's also worth noting _.each returns the list if you want chain some more manipulation after calling _.each. Here's a quick example showing how it can be used and what's available to you when you call it. With that out of the way, let's think about what this means in terms of cleaning up our code. To do the above normally we would write a little for loop like this. Admittedly these two aren't all that different, but let's imagine we have a function defined elsewhere that will deal with handling the arguments passed in on each iteration. We can replace that same functionality with a significantly less verbose solution. To quote Antoine de Saint Exupéry: \"It seems that perfection is attained not when there is nothing more to add, but when there is nothing more to remove.\" While it may not be perfection, there are certainly arguments to be made about performance, I think you would be hard pressed to find anything further simplify this code. While _.each will return the original list you input, _.map will allow you to manipulate or otherwise transform the input as you please and then returns the new array. Map needs a minimum of 2 arguments, first the collection and then the function to be executed on each iteratee and also accepts a third argument which dictates the context for the iterating function. Before you go writing some functions to pass as an argument to _.map be sure to take a peek at the other methods available in Underscore. Map is a little bit like having the Lego blocks to build whatever you want, but if you already have a pre-packaged Batcave available, it might not be the best use of your time building it from scratch. To illustrate my childhood toy analogy let's talk about _.pluck. Pluck is basically just a refined version of _.map made for a specific use case. That's not to say there aren't ways of combining the two to achieve something a little more complex, but if standard _.pluck behaviour is all you're after then don't go re-inventing the wheel. Often with data objects we're interested in the values of a specific key, for example let's say we have an array of movies. Now we want to just have an array of the titles of these movies. Not much else to say about it, it works on collections and is extremely handy for a very common task. Another example of a more refined _.map function that comes in handy often enough. Aptly named this method will return an array of only the things that make it through your test. Works on collections and kitchen sink faucets. Just kidding there's no _.conclusion method. I hope by now that you get the idea that if what you need to do isn't already a method, Underscore's _.map is a powerful tool for accomplishing whatever obscure collection manipulation your heart desires. So get out there, take a look through Underscore JS and start writing less obfuscated (nested) for loops with the help of _.each. LinkedIn has recently revamped their API systems and added many new restrictions. We will go through some examples on how you can utilize the LinkedIn Javascript API in order to setup some useful features that comply with LinkedIn's new terms and conditions and use cases. The first step will be setting up your login button which will prompt the user to authenticate with their LinkedIn credentials. We have provided a guide to getting a basic login button setup here. The linked guide will get you as far as setting up a button that allows your users to login with LinkedIn and display a personalized welcome message. Below we will go over extending this functionality to allow you to handle more complex features for your users after logging in. You can control and initiate specific behavior after a user logs in. You can assign these event handlers by first setting the function that will be used to initialize the events. This will trigger the event designation after the LinkedIn scripts have been loaded on your page. Update the LinkedIn initialization script: This will trigger the onLinkedInLoad function after the Linkedin scripts have been loaded. You can now assign some LinkedIn Event handlers in this function to control the behavior that will occur for different LinkedIn user actions. Let's begin by assigning the behavior that occurs after a user logs in. The above event will trigger when a user authorizes and will call the getProfileData function. We can add another event assignment for the user logging out. The above logout event will trigger the sendGoodByeMessage when the user logs out. Now that we have the basic event handling in place we can handle the specific behavior for users logging in. Once a user has logged in and triggered the getProfileData event we can pull in their user profile using the LinkedIn Raw data API handlers, these allow you to access any of LinkedIn's API endpoints and get data back. We will begin with a quick check to make sure the user is still authorized and then call the Raw API to pull in the people endpoint for the current user: If the data is successfully returned it will call the onSuccess function and if not it will call onError. These functions will both include a JSON formatted response that can be used to display their profile data or log a message: You can test the response formats for most of the LinkedIn APIs on LinkedIns API console You can access any of the API endpoints after successful login via the raw API handler and retrieve data per your requirements. Before making any API requests you should verify that your user has a current active session. User sessions are valid for 30 minutes by default. These sessions can be extended using the following call: The above call can be used to refresh the expiration time for the user but repeated calls may cause your app to be blocked so this should be used sparingly. You can provide the ability for your users to logout by setting up a button or link that will trigger the following function call: This will trigger the same function that was assigned to the logout event. If you're not familiar with Angular I'd highly recommend heading over to the Angular JS resource site and checking out what all the fuss is about. Once you've got a basic understanding of Angular and how to get it up and running this tutorial will show you some of the basic, but awesome features supported by Angular. Today I'm going to be building out a roster for my fantasy football team. If that's not your cup of tea then by all means feel free to substitute the content for whatever floats your boat. There might not be an I in team, but there are certainly players, so before we do anything in the HTML we'll have to make all the necessary components in the controller. First up let's make an array of all the players we want to include (initially at least) on our team. Every player is a special little snowflake, and our player objects should reflect that! With this in mind we will make each player an object with his or her own properties like: name, position and team. Here's an example of what our array might look like. Now that we have our roster we can go back to the HTML and make use of Angular's ng-repeat directive. We put the ng-repeat on the element we want to be repeated, keeping in mind that all of its children will also get repeated. Okay so if you're new to Angular there's a couple of things going on here. First like I said we've got the ng-repeat placed on the li (the thing we want repeated) which will create a new li for each player in the players array we defined earlier in the controller. Next up the data binding is being implemented here with each player name as well as position being used as the values for the list item. While we're on the topic of data binding, let's throw this in just for fun. Pretty simple, it will calculate the length of your roster and keep it updated as any changes are made. Next let's add some search functionality to our list. Sounds like a lot of work, probably have to iterate over the array elements, match them to the argument being passed in and... just kidding. With Angular it's a breeze. Donezo. Let's imagine one of our fantasy players isn't performing too well (ahem Peyton...) and we want to give him the boot (get it now?). We'll add a little delete button beside each of our players' names, and since we're doing it for each of them guess how we're going to implement it? That's right with ng-repeat we already have on the list items! I'll also tack on a little button with an \"x\" as the content (as a side note, when you want to do this use × instead of \"x\" it looks much nicer). Then we'll attach an ng-click with a delete function where we pass in $index. $index is a neat little feature available with certain Angular directives, and ng-repeat is one of them. It will be assigned the index value (starting at 0) of the position it holds within the array being used with the ng-repeat. That's all we need in the HTML, so now back in the controller we create a $scope function by the same name used in the HTML and give it a parameter of index. The body of the function is a single line which makes use of the array.splice method where we pass in the index of the item we want to delete, and then 1 to denote that it's only 1 item we want removed. Now since we just cut someone from the team, we've gotta find their replacement. Let's chuck a few text inputs in there, give them all a respective ng-model to bind with their value and finally another button with an ng-click but this time calling an addPlayer function. This one's a lil' different from delete, but still super simple. Working from the inside out, we will create a new player object which gets the name, position and team properties from the ng-models on the HTML and then push that object to the players array. After that we clear those values just for some good housekeeping practice. Now since this was all done purely on the front end, and didn't make use of cookies, localstorage, or sessionstorage none of this will persist (aka be saved). For that kind of support you'd need some sort of back end, which is beyond the scope of this article. This was a very rudimentary example of what's possible with Angular JS, so if this interested you at all please dig a little deeper and play around with Angular some more! That brings us to the end of this tutorial. Feel free to check out the finished (yet unstyled) product here on Codepen Identity is evolving, and developers are at the forefront of this transformation. Every day brings a new learning—adapting to new standards and refining approaches to building secure, seamless experiences. We’re here to support developers on that journey. We know how important simplicity, efficiency, and well-structured documentation are when working with identity and access management solutions. That’s why we’ve redesigned the LoginRadius website—to be faster, more intuitive, and developer-first in every way. The goal? Having them spend less time searching and more time building. LoginRadius’ vision is to give developers a product that simplifies identity management so they can focus on building, deploying, and scaling their applications. To enhance this experience, we’ve spent the last few months redesigning our interface— making navigation more intuitive and reassuring that essential resources are easily accessible. Here’s a closer look at what’s new and why it’s important: Developers spend long hours working in dark-themed IDEs and terminals, so we’ve designed the LoginRadius experience to be developer-friendly and align with that preference. The new dark mode reduces eye strain, enhances readability, and provides a seamless transition between a coding environment and our platform. Our new design features a clean, modern aesthetic with a consistent color scheme and Barlow typography, ensuring better readability. High-quality graphics and icons are thoughtfully placed to enhance the content without adding visual clutter. So, whether you’re navigating our API docs or configuring authentication into your system, our improved interface will make those extended development hours more comfortable and efficient. We’ve restructured our website to provide a straightforward breakdown of our customer identity and access management platform capabilities, helping you quickly find what you need: This structured layout ensures you can quickly understand each capability and how it integrates into your identity ecosystem. We’ve been analyzing developer workflows to identify how you access key resources. That’s why we redesigned our navigation with one goal in mind: to reduce clicks and make essential resources readily available. The new LoginRadius structure puts APIs, SDKs, and integration guides right at the menu bar under the Developers dropdown so you can get started faster. Our Products, Solutions, and Customer Services are also clearly categorized, helping development teams quickly find the right tools and make informed decisions. Developers now have a clear view of the tech stack available with LoginRadius, designed to support diverse business needs. Our platform offers pre-built SDKs for Node.js, Python, Java, and more, making CIAM integration seamless across popular programming languages and frameworks. Check out our revamped LoginRadius website and see how the improved experience makes it easier to build, scale, and secure your applications. Do not forget to explore the improved navigation and API documentation, and get started with our free trial today. We’re excited to see what you’ll build with LoginRadius!
\nTo confine MySQL from opening a network socket, the accompanying parameter ought to be included in the [mysqld] area of my.cnf or my.ini:
\nThis line cripples the start of systems administration in the middle of MySQL startup. It would be ideal if you bear in mind that a local connection can be used set up a connection to the MySQL server.
\nYou may not be willing to incapacitate system access to your database server if clients in your organization interface with the server from their machines or the web server introduced on an alternate machine. In that case, the following restrictive grant syntax should be considered:
\nmysql> GRANT SELECT, INSERT ON mydb.\\* TO 'someuser'@'somehost';
\nIn addition, in certain cases, the \"LOCAL INFILE\" command can be used to gain access to other files on the operating system, for instance \"/etc/passwd\", using the following command:
\nmysql> LOAD DATA LOCAL INFILE '/etc/passwd' INTO TABLE table1
\nmysql> SELECT load\\_file("/etc/passwd")
\nset-variable=local-infile=0
\nmysql> RENAME USER root TO new\\_user;
\nmysql> use mysql;\n\nmysql> update user set user="new\\_user" where user="root";\n\nmysql> flush privileges;
\nmysql> SET PASSWORD FOR 'username'@'%hostname' = PASSWORD('newpass');
\nshell> mysqladmin -u username -p password newpass
\nTo remove this database, use the drop command as follows:
\nmysql> drop database test;
\nshell> mysqladmin -u username -p drop test
\nmysql> select \\* from mysql.user where user="";
\nmysql> SHOW GRANTS FOR ''@'localhost';\n\nmysql> SHOW GRANTS FOR ''@'myhost';
\nshell> mysql -u blablabla
\nmysql> DROP USER "";
\nmysql> use mysql;\n\nmysql> DELETE FROM user WHERE user="";\n\nmysql> flush privileges;
\n* Any new MySQL 5.x installation already installed using the correct security measures.
\nTo protect your database, make sure that the file directory in which the MySQL database is actually stored is owned by the user \"mysql\" and the group \"mysql\".
\nshell>ls -l /var/lib/mysql/var/lib/mysql.
\nThe mysql binaries, which reside under the /usr/bin/ directory, should be owned by \"root\" or the specific system \"mysql\" user. Other users should not have write access to these files.
\nshell>ls -l /usr/bin/my\\*
\nOn the other hand, some user ids are used to access the data, such as the user id assigned to the web server to execute \"select\\update\\insert\\delete\" queries and to execute stored procedures. In most cases, no other users are necessary; however, only you, as a system administrator can really know your application’s needs.
\nmysql> use mysql;
\nmysql> select \\* from users;
\nmysql> show grants for ‘root’@’localhost’;\n
\n/etc/my.cnf:
\nskip-show-database /etc/my.cnf file:
\nlog =/var/log/mylogfile
\nIn addition, verify that only the \"root\" and \"mysql\" ids have access to these logfiles (at least write access)./chroot/mysql In addition, to make the use of the database administrative tools convenient, the following parameter should be changed in the [client] section of MySQL configuration file:
\nsocket = /chroot/mysql/tmp/mysql.sock--socket=/chroot/mysql/tmp/mysql.sock parameter every time these tools are run.
\nWe should remove the content of the MySQL history file (~/.mysql_history), wherever all dead SQL commands are kept (especially passwords, that are kept as plain text):
\ncat /dev/null > ~/.mysql\\_history_.each
\n
\nvar someArray = ["a", "b", "c"];\n \n_.each(someArray, function (element, index, list) {\n console.log("value: " + element + " index: " + index + " list: " + list)\n});\n \n// outputs\nvalue: a index: 0 list: a,b,c\nvalue: b index: 1 list: a,b,c\nvalue: c index: 2 list: a,b,c
\nfor ( var i = 0; i < someArray.length; i++) {\n console.log("value: " + someArray[i] + " index: " + i + " list: " + someArray);\n}
\n_.each(someArray, doStuff);_.map
\n
\nvar numbersObject = {1:1, 2:4, 3:9};\n \nvar productArray = _.map(numbersObject, function(value, key) {\n return value * key;\n});\n \n//proudctArray is now\n[1, 8, 27]_.pluck
\n
\nvar movies = [\n {title: "Dracula", genre: "Horror", star: "Nosferatu"},\n {title: "Cast Away", genre: "Drama", star: "Wilson"},\n {title: "Airplane", genre: "Comedy", star: "Leslie Nielsen"}\n];
\nvar titlesArray = _.pluck(movies, 'title');\n \n//titlesArray is now\n["Dracula", "Cast Away", "Airplane"]_.filter
\n
\nvar numbers = [1,33,6,24,8,21,11,22];\n \nvar lessThanTen = _.filter(numbers, function(number) {\n return number < 10;\n});\n \n//lessThanTen is now\n[1, 6, 8]_.conclusion
\nGetting Your Site Ready
\nEvent Handling
\n
\n<!--\napi_key: \nauthorize: true\nonLoad: onLinkedInLoad\n-->
\n<!--\nfunction onLinkedInLoad() {\n IN.Event.on(IN, "auth", getProfileData);\n}\n-->
\n<!--\nfunction onLinkedInLoad() {\n IN.Event.on(IN, "auth", getProfileData);\n IN.Event.on(IN, "logout", sendGoodByeMessage);\n}\n-->Data Retrieval and API access
\n
\n<!--\nfunction getProfileData() {\n if(IN.User.isAuthorized())\n IN.API.Raw("/people/~").result(onSuccess).error(onError);\n}\n-->
\n<!--\nfunction onSuccess(data) {\n console.log(data);\n}\nfunction onError(error) {\n console.log(error);\n}\n-->User Management
\n
\n<!--\nIN.User.refresh()\n-->
\n<!--\nIN.User.logout(sendGoodByeMessage);\n-->Players Array
\n
\n$scope.players = [\n {name: "Tom Brady", position: "QB", team: "Patriots"},\n {name: "Tony Romo", position: "QB", team: "Cowboys"},\n {name: "Peyton Manning", position: "QB", team: "Broncos"},\n {name: "Rob Gronkowsi", position: "TE", team: "Patriots"},\n {name: "JJ Watt", position: "DE", team: "Texans"},\n {name: "Lavonte David", position: "LB", team: "Buccaneers"}\n];Repetitive department of repetition
\n
\n<!--\n {{player.name}} - {{player.position}}\n-->
\n<!--You have {{players.length}} on your roster.-->Easiest Search Functionality of Your Life
\n
\n<!--\n...\n{{player.name}} - {{player.position}}\n-->The shape of Italy
\n
\n<!--{{player.name}} - {{player.position}}\n ×\n-->
\n$scope.delete = function (index) {\n $scope.players.splice(index, 1);\n};Acquisitions
\n
\n<!--\n Name:\n \n Position:\n \n Team:\n \n Add Player\n-->
\n$scope.add = function () {\n $scope.players.push({\n name: $scope.new_name,\n position: $scope.new_position,\n team: $scope.new_team\n });\n $scope.new_name = "";\n $scope.new_position = "";\n $scope.new_team = "";\n};Nothing Lasts Forever
\nWhat’s New and Improved on the LoginRadius Website?
\nA Developer-Friendly Dark Theme
\n![\"This](\"/f46881583c7518a93bb24e94c32320de/a-developer-friendly-dark-theme.webp\")
Clear Categorization for LoginRadius Capabilities
\n![\"This](\"/e5358b82be414940f3fb146013845933/capabilities.webp\")
\n
\nDeveloper-First Navigation
\n![\"This](\"/a8c155c2b6faf3d5f4b4de4e2b14d763/developers-menu.webp\")
Quick Understanding of Integration Benefits
\n![\"This](\"/b2f9a964a2da0ea83e2f8596b833bba7/we-support-your-tech-stack.webp\")
Over to You Now!
\n