Click here to register or to donate.Auto self-registration is not available here - far too many spammers. This forum has many, many backlinks and because of that there is an intense desire among spammers to drop their links here.

[SOLVED] Can't Export Setting Anymore

#1

May 25, 2011, 09:05 PM

dingest

15 posts · Oct 2010

I have three Atahualpa sites and none of them allow me to export the settings file anymore. When i hit the export it just takes me to the home page of the website. Previously it would send the txt file my download folder.

Two sites are 3.4.9 and one is 3.6.7.

Thanks for your help.

#2

May 25, 2011, 11:01 PM

juggledad

23,596 posts · Mar 2009

OSX 10.11.5 WP 4.x Atahualpa(all) Safari, Firefox, Chrome

What has changed? If you added a new plugin, disable it. In fact temporally disable all plugins and see if it worked.

If you did do anything, then ask your host what changes they have made.

__________________~Larry (CNY Web Designs)
This site should be a membership site since it so full of good stuff.
Please consider donating which gives you access to even more good stuff.

#12

May 28, 2011, 11:01 AM

deuxetoiles

44 posts · Dec 2009

Okay, I'll try it, but that's not the root of the site, so can you explain, please?

#13

May 28, 2011, 11:09 AM

deuxetoiles

44 posts · Dec 2009

I changed the Site address (URL) and it worked. I think I understand why. http://www.simongoland.com/home/ is going to the current, non-WP site, so Atahualpa gets confused.

Thanks!

#14

May 28, 2011, 11:54 AM

lmilesw

10,174 posts · Jul 2009

Central New York State USA

It IS the CURRENT root however. When the site moves you will have to change those addresses again.

__________________~Larry (CNY Web Designs)
This site should be a membership site since it so full of good stuff.
Please consider donating which gives you access to even more good stuff.

#15

May 28, 2011, 04:47 PM

deuxetoiles

44 posts · Dec 2009

Just for the record, changing the site url to any other page on the site made the export work, even though it is not the root of the site. I think this because the actual root is currently conflicting with the index.html file already there.