Looks likes that bit of code actually worked.
Still spews a lot of similar errors, but the csvs were processed. I'll just redirect the garbage into /dev/null and hope it will get clean up at some point.
The good thing is, it's working.
Now that we're on the topic of automation. Any thoughts about crontabbing status of categories ?
I'm thinking of doing something like this right after the cron ep4_cron job to toggle the status of the category.
mysql --user=[username] --password=[password] < [script pathway]
—————SCRIPT——————
update products set catagories_status=1 where catagories_id = [product to be toggled];
mc12345678:
It's relatively new and incorporated to help someone that had asked for the possibility and didn't know how to put together the bits that would be necessary for its execution, so yes, little to no documentation other than what is in the file itself.
As for the warnings received, that's because the language file is not pulled into the cron and not into the import portion. Furthermore it's because the import file does more than just import, it also prepares text to be exported, but does not actually export text.
So, to get those messages to go away, I am thinking the following would work.
In line 332 of admin/ep4_cron.php add the following:
if (isset($_SESSION['language']) && file_exists(DIR_FS_ADMIN . DIR_WS_LANGUAGES . $_SESSION['language'] . '/easypopulate_4.php')) {
require DIR_FS_ADMIN . DIR_WS_LANGUAGES . $_SESSION['language'] . '/easypopulate_4.php';
} else {
require DIR_FS_ADMIN . DIR_WS_LANGUAGES . 'english'. '/easypopulate_4.php';
}
>
> With the require for the import file being at line 339 as it may seem.
>
> My ISP is having some serious issues so I am limited on what I can test, confirm, and manipulate basically by what my cell phone can do or what can be done with limited cell phone data tethering.
