Strategerizer

I also tried to Network Deactivate and then Activate only for that subsite but it will still not show up…

?

VatosKorea, did you figure it out? I am having the same issue…

Looks like issue gets resolved if I add “zip” as an allowable file type to be uploaded.

I am wondering if security will be better if I do not add zip as a permissible file type, in which case…

FEATURE REQUEST: Change settings export/import file type from .zip to .txt.

Thanks!

I’d like to have the solution generalized…

What is the simplest way to have a child theme change some function from the parent theme??

I understand that the child theme’s functions.php get loaded first so putting there the modification is useless. I also don’t want to change anything in the parent files that will break when the parent theme gets updates. Unfortunately, the parent theme does not have provide for an easu way with “if function exists…” statement.

Thanks!

OK, I’ll investigate that; thanks.

Mapped domains; the client will need to have their subsite appear at their own company URL.

I probably can’t use rules for the redirects, rather one-by-one mapping for each of the old static .htm files to the new WP subsite path. My concern is having a hundred of those redirects in the main supersite .htaccess file. Is there a better way?

Do you have any more specific feedback or pointers?

Aha… those two sites have the Disqus Comment System plugin and disabling it bring back the right value.

Update: Actually it looks like there is an issue with the supersite (the main network site) as well – displays the space used as simply “5” (without showing a unit measure such as “MB” or a percentage of use as on all other sites.)

@andrea_r, you mention…

I’d transfer all the files over, temporarily use the old domain on the new server, make sure it works, THEN change the domain.

When I try that I have issue verifying the new multisite, on the new server, and using the same domain as the old server. Since the DNS points to the old server, I can’t seem to see the files on the new server; the files from the old server come up instead.

I can verify files on the supersite (main site) using the new server ip address but not sure how to verify files for the subsites.

Any ideas?

Good to know; thanks.

@ipstenu, related to 32-bit vs. 64-bit – have you encountered any compatibility issues with sw you needed to install on the 64-bit server? I know that with desktop environments even now there are some issues with some apps/drivers on 64-bit Windows computers. Are there any such concerns related to servers?

I have a choice of either and just set up cloud hosting using 32 bit to avoid those hypothetical problems but if you think my worry is unwarranted, I’ll redo the setup using a 64-bit cloud “server”.

Thanks for the practical guidance; that’s surprisingly great news!!

Without an accessible server monitoring and performance charting app, I had little idea on my private server utilization. It is good to know that WP demands a lot less of the server than I initially thought.

@andrea, to clarify the limitation I was encountering on the client’s registrar DNS setup screen…

Trying to set up a CNAME for www. client7.com to go to supersite-network.com, it was telling me that an A record exists for that subdomain (www). Based on that I assume that I need to delete the A record in order to let me do it.

However, even after deleting, I still could not complete the setup (based on using the CNAME option) because the registrar would not let me create a CNAME for the base domain (to have client7.com – without the www subdomain – point to supersite-network.com). The ui has a field for the subdomain I want to create the CNAME for and it gives error if left empty. I tried using “@” but it only accepts alphanumeric, * and -.

Hey Ipstenu, I guess you weren’t kidding!

OK, so my understanding is some registrars have limitation on CNAME not being avaialable for TLD.

So the end user (subsite admin) will not be able to reliably set a CNAME for their website (at least if they don’t want https://www., such as https://client7.com) that would allow them to map to their WP subsite (e.g. https://client7.supersite-network.com).

Assuming my understanding is correct, the super-admin should NOT use the CNAME option for Domain Mapping when setting the plugin. It can lead to the end user not being able to map the website they want to their subsite. We will have to hardwire to IP address. This will require the end user to use A records to map their domains (https://client7.com, https://www.client7.com) to that IP address.

I hope I got this right… just too important to screw this up.

Thanks for your input on this; much appreciated.

If you have interest in the topic, see my initial thread on the larger topic…

https://www.ads-software.com/support/topic/plugin-wordpress-mu-domain-mapping-primary-vs-secondary-domain-used-for-www?replies=10

The Domain Mapping plugin author replied but too succinctly to illuminate the topic completely, at least for me.