Easy Populate 1.2.5.4 support

Quote:

---

Originally Posted by langer

which means?!?

---

ITS ALOT OF MOOLA

Quote:

---

Originally Posted by langer

This is a server issue. Your host may be able to resolve this.

The follwing in your .htaccess file might work:

Code:

---

<IfModule mod_security.c>
# Turn off mod_security filtering.
SecFilterEngine Off

# The below probably isn't needed, but better safe than sorry.
SecFilterScanPOST Off
</IfModule>

---

---

Exactly. mod_security scans the contents of things being sent through the browser and stops things it thinks may be rogue. Typical things it will block are SQL commands like INSERT INTO and DROP TABLE and CREATE TABLE and so on. There are numerous others as well. This is the same reason why the SQLPatch tool has problems on some servers and throws the 406 error.

Woody, I see you have resolved your dilemma, but it sounded like you were looking for more information... hence this bit of clarification.

Quote:

---

Easy Populate uploads folder not found!
NIX SERVERS: Your uploads folder is either missing, or you have altered the name and/or directory of your uploads folder without configuring this in Easy Populate.
WINDOWS SERVERS: Please request your web host to assign write permissions to the uploads folder. This is usually granted through Windows server user account IUSR_COMPUTERNAME.
Your configuration indicates that your uploads folder is named temp/, and is located in /home/content/a/p/i/apinkpony/html/shop/, however this cannot be found.
Easy Populate cannot upload files until you have provided an uploads folder with read/write/execute permissions for the site owner (usually chmod 700 but you may require chmod 777)

---

Thats what I got this time when I uploaded it. I'm insure why it tells me my upload folder is named temp, I didnt do anything with a folder named temp! I just did exactly what the directions told me to do.

Nevermind, I figured it out. I'm dumb.

the older version still works on version 3 right??

I'm using easypopulate 1.2.5.4 and I'm getting a 500 Internal Server Error with this:

Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.


This is what the error log says:

[error] [client myIPhere] Premature end of script headers: /pathhere/easypopulate.php


I've already contacted my host and I'm waiting on a reply. I just wanted to know if this is an easypopulate error or something to do with my host?

Thanks.

What happens if I don't reset the admin activity table log? I am nervous my entire site will delete!

Quote:

---

Originally Posted by jillkap

What happens if I don't reset the admin activity table log? I am nervous my entire site will delete!

---

Then the log will keep growing bigger and bigger consuming more and more space in your hosting account. You can safely purge older records using the Tools->Store Manager button for cleaning up old records.
The activity log is only useful for audit-trail issues in case there is an inquiry about who's been doing what or accessing customer data in your admin area.
If you want to retain the history, simply do a backup of the table before pruning.

Quote:

---

Originally Posted by tj1

I'm using easypopulate 1.2.5.4 and I'm getting a 500 Internal Server Error


This is what the error log says:

[error] [client myIPhere] Premature end of script headers: /pathhere/easypopulate.php

---

"when" are you getting this error? What clicks can reproduce it?

Quote:

---

Originally Posted by DrByte

"when" are you getting this error? What clicks can reproduce it?

---

Hi DrByte, this happens anywhere in the 2 to 5 minute mark.

If I upload a relatively simple file with say, less than 1000 products, it seems to work just fine. It just happens with the larger files that require more processing time.

I'm not sure you can reproduce it. It's pretty straight forwared, I just go to Tools>Easy Populate, select the file I want to upload and click insert into DB.

What I'm trying to find out is if this is an issue with EasyPopulate or with my host.
I think it might be my host, because I've used EasyPopulate successfully on the past and I haven't changed or done anything different.

My host has asked me if I can add something to the script so I can see where it's stopping. But that's just way beyond my knowledge.
I know EasyPopulate has a 'debug logging' option, which is enabled, but so far it hasn't generated any logs.