May 18 2022

Change WordPress Login Page without a PlugIn

WordPress is the most popular way to create your website or blog. It is an open-source content management system that allows you to manage important aspects of your website without knowing anything about programming. WordPress also supports plugins, which are small applications that work within the software framework to offer additional functionality. 

This blog is running WordPress (I am not giving away any big secret as it is easy enough to find this out). WordPress has the popularity, leaving many “bad actors” who try to compromise WordPress sites with brute force login attacks. There are plugins available, such as Limit Login Attempts Reloaded, that help prevent malicious attacks targeting your login page. With this plugin, you can limit the number of failed login attempts and lock out users who attempt to login incorrectly on several attempts.

Another way to protect your WordPress Site from brute force login attacks is to change your login page. Changing your login page makes it more difficult for malicious login attempts because your login is not one of the known login pages. Several plugins are available for you, but it is easy to do without adding additional plugins to your site. Using a Plugin generally does not require any programming knowledge. Please note that doing this without a plugin  does require some programming knowledge, and before ever making any changes, you should always back up your site.

  1. The default login page is wp-login.php. Download this file from your website and open it with a text editor.
  2. Replace all occurrences of wp-login.php in the file with the name of the file you’d like for your login page (keep the PHP extension)
  3. Save the file with the same name you replaced the wp-login.php page value with in the file.
  4. Delete or rename the old wp-login.php file
  5. Upload your new login file
  6. You can now log in using the link <homepage WordPress baseurl>/<your login page>; replace the values with your values.

WordPress allows for filter hooks to override specific actions within the framework. After you rename the login page, you should set a few hooks to properly redirect a user when they log out of your site.

add_filter( 'logout_url', function(){
	$login_url = wp_nonce_url(site_url('.php')."?action=logout", 'log-out');
	return $login_url;						  
}, 30, 2);

add_filter( 'logout_redirect', function() {return esc_url( home_url() );}, 30, 2 );

The above hooks will set urls to use when a user logs out of your site and the page they will be redirected after the logout.

Add the hooks to the functions.php file of your theme. Make a note and save the code for the hooks added. If the function.php file is updated and replaced the hooks will need to be added to the file again.

Note: There is a hook for the ‘login_url’ if you want the default login to route to your new page. Setting the hook does make the page visible again as a different page name. Do not set the hook if you intend to mask this page to make it more difficult to find.

May 14 2022

Business Central 2022 Wave 1 – Multiple Report Layouts in Reports and Report Extensions

With each update of Dynamics 365 Business Central, Microsoft enhances what is often referred to as the base application and enhances the development environment. Dynamics 365 Business Central 2022 Wave 1 has several exciting new features in the development environment. One of the exciting features is the option for multiple report layouts within a single report or report extension. This provides report developers the option to add alternative layout options in a single report or report extension.

In earlier versions of Dynamics 365 Business Central, you could only embed a single layout of each report layout type (RDLC or Word) in a report or report extension. If there were a need to have additional layouts, the layout was setup as Custom Report Layout. In Dynamics 365 Business Central 2022 Wave 1 a new Rendering section has been added; you can now include multiple layouts of different or the same type.

Rendering Section

Rendering Section

To enable multiple layouts, you must use the Rendering section of a report object. Inside the Rendering section, you define one or more layout sections. In each layout section, you specify details about the layout file path and name, a Caption property, and a Summary property, which is displayed to the user on the Report Layouts page in Dynamics 365 Business Central.

The default layout is defined with the DefaultRenderingLayout report property. Note: This DefaultRenderingLayout property cannot be set on report extension objects, only on report objects.

DefaultRenderingLayout Property

DefaultRenderingLayout Property

When a report with multiple layouts is loaded, the report layouts are visible on the Report Layout Page. The layout is selected on the Report Layout Selection Page.

Note: The old properties for defining RDLC, Word, and the default layout, still exist but cannot be used in combination with the new rendering section. A report author must use one or the other.

See What’s new and planned for Dynamics 365 Business Central for additional information.

May 13 2022

Repository-specific username/email configuration

You set up your repository. You cloned the repository and made some changes. You commit your changes and get the error – Make sure you configure your ‘user.name’ and ‘user.email’ it git

Make sure you configure your 'user.name' and 'user.email' it git

When working with Git as a source control management tool, you need to have defined the user name and email config value when checking in code. These values identify the user in commits. If you don’t have these configured, you’ll see a message – Make sure you configure your ‘user.name’ and ‘user.email’ it git

The username/email configuration can be set globally or at the project level.

To set your global username/email configuration:

  1. Open the terminal command line.
  2. Set your username: git config ––global user.name “<your name>”
  3. Set your email address: git config ––global user.email “youremail@example.com”

To set repository-specific username/email configuration:

  1. From the command line, change into the repository directory.
  2. Set your username: git config user.name  “<your name>”
  3. Set your email address: git config user.email “youremail@example.com”

Verify your configuration by displaying your configuration value –

git config ––get user.email
git config ––get user.name

May 11 2022

Hello, World!

If you are new to or familiar with computer programming, you’ll most likely be familiar with “Hello, World!”

“Hello, World!” is typically the first program that someone learns to write and is often used to test that the compiler is installed correctly.

I am not new to blogging and community involvement; however, I have stepped away from it for a while and wanted to get back into it and share my experiences and what I learned along the way.

Well, friends, this post is my “Hello, World!” for this site.