lernerconsulting

Never have the user name ‘admin’, all hackers know the default WordPress user name; iThemes Security has an option to change it for you.

If nobody knows your login name, and nobody can guess it, they can’t brute force attack your login.

So, don’t display the user name anywhere on the site. In the Profile page (/wp-admin/profile.php or /wp-admin/network/profile.php), for Each user, set the Nickname and set “Display name publicly” as the nickname.

Try the “Media from FTP” plugin, which searches for files uploaded by FTP into the Uploads folder, and adds them to Media Library. Optionally reads file date or meta-data to move into year-month folders.

Does maindomain.com/wp-admin/ still bring up WordPress Dashboard? It must. If it doesn’t check things like redirection in .htaccess

newdomain.com should (before you do any domain mapping) load WordPress, displaying the same page as maindomain.com.

asdf.maindomain.com should bring the WordPress “do you want to make a new site” page. That’s a good test of “wildcard DNS” working.

Have you used WordPress to create a site “newdomain”? If you configured multi-site in “subdomain” mode, the site newdomain would have URL newdomain.maindomain.com

Get all this working, before you attempt anything with domain mapping.

https://lcblog.lernerconsult.com/2012-wordpress-3-multi-site-domain-mapping/

Once the 2nd site exists, like Ron mentions (you have to create it first in WordPress, before you can map a domain name to it)…

I cover one set of working options for
wp-admin/network/settings.php?page=dm_admin_page
and how to find the Site ID to put in
wp-admin/network/settings.php?page=dm_domains_admin
in my Domain Mapping instructions

Domain Mapping Plugin works for me on WP4.3

Davinian, on /wp-admin/network/sites.php change the “Screen Options” (top right of page), “Number of items per page” from 20 (the default, if I remember right, for long time), to 999. (Nothing to do with the Domain Mapping plugin.)

@jsghagan – I am wondering still what you need to do this for. Do you need to retire olddomain.com and replace it with newdomain.com? You can change the domain that WordPress runs on. (You can’t map the domain for Site 1; you can completely replace the domain.) Changing that would be related to the process for moving WordPress single-site to a different domain name, except needs to check for olddomain.com in the additional tables for multi-site. Moving multi-site from development server to production server would require the identical process, if this is what you want.

I’ve never documented the steps for this. Somewhere I have notes which search/replace plugin I used. It would have to know about WordPress “serialized data” and multi-site tables.

Step 1, obviously, is Backup Your Data!
Step 2, backup again, to a different file name.
Step 3, I’ve heard prayer is always good.
Step 4, would you let us know what works, if this is even what you’re looking for?

The plugin definitely works fine with WordPress 4.2 and 4.3

lynnakvo says in another of her support posts that she gave up on this plugin for her installation

jsghagan, What are you wanting to do?

If you have created another site on your multi-site, and you want to map a domain name to it, you put the Site ID of the “another” site into the domain mapping screen, not the ID of the main site.

Is domain mapping working for any sites? You may not have the plugin files in the correct places…

This may help, though forgive me for just guessing:
https://lcblog.lernerconsult.com/2012-wordpress-3-multi-site-domain-mapping/
(updated enough so still works with WordPress 4.3)

For checking your server logs, you’ll have to ask your hosting technical support, every host has their own place for them.

The Ottopress instructions are so ancient they no longer are clear, including different terms and locations for the WordPress menus.

My instructions from 2012 have enough updates to include the latest version of the plugin. Covers what some of the options do, and also has installation and troubleshooting.
https://lcblog.lernerconsult.com/2012-wordpress-3-multi-site-domain-mapping/

For your “3rd site” problem, you might be giving an incorrect “Site ID”, that is a common mistake (and Ottopress doesn’t cover it).

Can’t tell from your short description. so here’s some things to check:

You can’t have domain mapping for the main site, the site that you use wp-admin from. For the domain mapping to work, WordPress itself has to be on an un-mapped domain. https://www.mysite.com/wp-admin/

For DNS to work on shared hosting and most other configurations (i.e. unless you’re a server expert and want a lot more work!) you can not install WordPress in a subfolder and do domain mapping. You can, however install WordPress in the Root of a Parked Domain or Add-on Domain. https://www.mysite.com/wp-admin/ not https://www.mysite.com/blog1/wp-admin/

Ron Rennick says in one of these support messages, “Domain parking is mainly a cPanel term. Most other web host control panels call it a domain alias. If you are using cPanel then parking the domain is the preferred implementation (over using an addon domain).”

My detailed installation and configuration instructions:
https://lcblog.lernerconsult.com/2012-wordpress-3-multi-site-domain-mapping/

p.s. The Domain Mapping development version works best:
https://www.ads-software.com/plugins/wordpress-mu-domain-mapping/developers/
click on the Current Version link, currently 0.5.5.1

LumberHack and johanponken and kirkward:

I have several WordPress version 3.3 multi-sites for myself and clients, using the wordpress-mu-domain-mapping development ver 0.5.5.1 and it works well with no error messages or problems.

You can “push the button” now. Yes, if you can wait, WP 4.4 will be good, but that is a “long time”.

From https://www.ads-software.com/plugins/wordpress-mu-domain-mapping/developers/ click the “Current Version” link, aka
https://downloads.www.ads-software.com/plugin/wordpress-mu-domain-mapping.0.5.5.1.zip

My 2012 instructions are still good (I’ve done minimal updates to keep it current):
https://lcblog.lernerconsult.com/2012-wordpress-3-multi-site-domain-mapping/

@panthony54, If you can’t see the widget configuration, you’ll have to edit the bad code via phpMyAdmin (or whatever MySQL editing tool you use).

select * from wp_options where option_name like ‘%widget_logic%’

Once you’ve seen the records, you can edit the ones with bad code in them. Warning: Errors in editing the MySQL database directly, can cause “big problems”. If you’re not knowledgeable about phpMyAdmin, Keep Out; find someone who is.

Basically, the Widget Logic plugin has no error checking, no debugging, no way of removing bad entries. That whole box where you should put valid PHP allows invalid PHP, or HTML, or anything else. Either never use that box, or find another plugin.

Does your example here exactly match what is in your site? Open curly brace paired with close parenthesis?

Does your custom plugin define a function is_artists() ? If so, is it accessible from outside your plugin?

try putting the Page ID, Page Title or Page Slug in is_page(), e.g.
is_page("aryn-michelle-concerts")

See https://codex.www.ads-software.com/Function_Reference/is_page

The plugin clearly says it evaluates Your code, the error is on line 1 of what SRD75 (or Someone) put it. The error is not line 1 of the plugin, it is triggered at line 286 of the plugin.

You have to use valid PHP, and it has to return a true/false result; RTFM.

If anyone puts HTML in that field, the angle bracket will cause a PHP Fatal Error; you may have to remove it in phpMyAdmin == Don’t!

The whole field is a security risk, since you can eval() a string that has malicious contents…

https://perishablepress.com/block-bad-queries/
based on their work developing a thorough .htaccess malware blocker
but as a WordPress plugin it is much easier to install.

For a client’s site, analyzing the server access logs, tracing who accessed that file and what other files they accessed, it became pretty clear it started with a vulnerability in a plugin.

Sucuri and iThemes Security plugins, both working together, add a lot. Backup first! Then turn on a single option at a time so if something doesn’t work in your environment or with your plugins, you know what to undo.

Remember that with very few exceptions, no PHP in wp-includes/ or wp-content/ should ever be loaded directly.

# based on Dre Armeda https://wordpress.tv/2013/02/01/dre-armeda-how-anyone-can-hack-your-wordpress-site-in-less-than-5-minutes-and-what-you-can-do-2/?relatedposts_exclude=28240
SetEnvIf Request_URI (?i)^/(wp-includes|wp-content|uploads|wp-admin/includes)/(.*)\.php$  badRequestString=$0--$1
SetEnvIf Request_URI (?i)^/wp-includes/ms-files.php$ !badRequestString
SetEnvIf Request_URI (?i)^/wp-admin/admin-ajax.php$ !badRequestString
SetEnvIf Request_URI (?i)/wp-content/cache/supercache/ !badRequestString
Deny from env=badRequestString