Search results

You *REALLY* shouldn't be pushing SQL in an ajax request. That is entirely insecure, and is the reason things like ModSecurity exist.

It is not missing. Your account is located on two servers, and currently the logon system is pointing you to the wrong server.

We're aware of this issue. It's partially related (right now) to the login system maintenance that occurred last night.

This is a result of the logon systems maintenance that occurred last night. I'm working on a fix for it right now. It's currently only affecting some accounts. I'll update you once it's resolved.

This is a result of the logon systems maintenance that occurred last night. I'm working on a fix for it right now. It's currently only affecting some accounts. I'll update you once it's resolved.

Hi, I apologize for this. This was due to the login maintenance earlier. You should be all set now.

When was the last time you opened your account? There is literally no trace of your account anywhere on our systems. I've recreated you an account... however any files or databases you had are gone.

Can you please try again now?

The script is most likely being killed because it is taking too long to run. What exactly are you doing to backup the database? I'd recommend using this script. http://sourceforge.net/projects/pmbackup/

You removed a theme without changing the theme from the admin panel. You will need to re-upload the theme and then uninstall it before removing it. (Loneley-road is the theme) You can try modifying the database, too.

Correct! There is no way to change it, as the systems are all linked together.

Your theme has an error in it. root@xo4 [/home/wptestse/www]# /opt/alt/php55/usr/bin/php index.php Parse error: syntax error, unexpected end of file in /home/wptestse/public_html/wp-content/themes/simple-black-and-white-theme/functions.php on line 25

Working on this with our management team today. Sorry it slipped through the cracks.

You can use software you have to pay for.. but you have to pay for it.

We're working on a full fix for this. I haven't gotten to patching free yet in the mean time

I'd do this by storing each individual record as a uuid, and then using the first few bytes as the "unique" string (since that's what a UUID is..) I'd store that in a table with that as the primary key, and then a few other columns (time_created, time_updated, etc) and whatever other info you...

In reality, only the Cache-Control header is necessary to stop the caching. Trust us--we've been using it for months...

guys.. guys. GUYS. This thread's 6 years old. Locked.

What is your domain name or username?

Hi-- Your email is not hosted by us. Your MX records point your domain to Google, meaning that you should be creating the email accounts from within your Google Apps admin panel. Any changes you make on the hosting server here have no affect on your actual email.