jon

I’m not sure that I completely understand what your problem is, but I would suggest reading this:
https://codex.wordpress.org/Giving_WordPress_Its_Own_Directory#Using_a_pre-existing_subdirectory_install

The “Using a pre-existing subdirectory install” section defines the best way to do what you tried to do.

If that does not solve your problem, please respond here.

No, that generally won’t work, at least not as simply as you are saying.

Why not just point a new domain at the old site? That will still require some work to change the Site’s URL.

There are lots of other possibilities. This documentation covers them pretty well:
https://codex.wordpress.org/Moving_WordPress

Hard to say if 1024MB will be enough. Probably, but no promises. GoDaddy has been known to limit resources pretty tightly, so you really don’t know if “Resource limit is reached” is referring to RAM. Again, probably.

If you are not using PHP 7, this could be a processor issue, as I had a Raspberry Pi that took 7-15 seconds on a page click in WordPress Admin on PHP 5. 100% CPU-bound.

PHP 7 generally requires half or less the CPU (processor) time.

If it were me, I’d try for a refund, if you are within their money-back window, which varies by vendor from 30 to 100 days.

Not sure who told you to contact wordpress.org support, but this appears to be a problem (or non-problem, depending on how accurate ismyblogworking.com is) with how WordPress was set up by Wealthy Affiliate on SiteRubix.com.

You will need to get your support from siterubix, as it sounds like they will have to fix it, and you will not be able to do it yourself.

Since my experience with VPS says you need MORE than 1GB RAM to do much of anything in WordPress, I suspect the same holds true for GoDaddy, though I don’t know what they count as part of that 512MB. For example, in a VPS, my “more than 1MB” number includes Apache, MySQL and the hundreds of other pieces of software that are part of a typical Linux web server.

The most likely reason that you are seeing a memory problem as the only authorized visitor to your site, is because the reality is that almost all web sites with a public URL are being visited by bots, hackers, and such sometimes several times a second.

Since I’m seeing people on these forums unable to run their Admin panels without increasing their PHP memory limit past 256MB (remember, that number is Per Use, and on top of Apache, MySQL and other memory usage), it does not take much to go past 1GB total RAM usage.

@kobashicomputing makes a valid point: “Discourage search engines from indexing this site” in Settings-Reading on the WordPress Admin panel of the test site is a very important step. Personally, I’ve been running test sites on public domain names for 8 years without any issues, and found it is sometimes essential, for example, for plugins and other services that need to communicate to a public URL from an external site.

On the other hand, I’m not a fan of installing WordPress on your test site and copying stuff over from your real site. Cloning is a lot less error-prone, especially when done with a tool like the Duplicator plugin, when it works properly (it works better on some types of web hosting environments than others).

Works for me in Firefox on a Desktop machine.

How long ago did you change the Name Servers at your Domain Registrar? It can take up to 72 hours to travel to all points worldwide.

I’m fresh out of ideas. Hopefully, someone else has some.