Thread

Curtis, let’s have you try something else for a moment.

Here’s a quick test to output to the screen once a minute. Create a brand new template and allow for PHP parsed on Input.

<?php echo date('G:ia'); ?> 

{exp:cron minute="*" hour="*" day="1,12,15,31" month="*"}

Displays this content once every minute of every hour on the 1st, 12th, 15th, and 31st day of every month.

{/exp:cron}

Debug: Outside of Cron stuff!

Does that work?

Yes it does.

Hi Curtis,

If the Blacklist module does write to your .htaccess file properly in the CP and the cron plugin does work on that test template then let’s just confirm that it isn’t actually working. Firstly, you should have a new folder in your system/expressionengine/cache folder called ‘cron’. Do you? Secondly, with the cron and cron_blacklist plugin installed correctly this test code on a template should work:

{exp:cron minute="*" hour="*" day="*" month="*" plugin="cron_blacklist"}{/exp:cron}

The way to tell whether it is working is to FTP into your server and make sure that your FTP client can show columns for file edit dates and times. If you refresh your template with that code on over the course of several minutes does the timestamp of the .htaccess file also change to reflect that it’s been updated?

Cheers

Greg

I do have that folder.

The code isn’t working, timestamp doesn’t update.

Tried uninstalling the blacklist/whitelist module and removing both plugins. Then I reinstalled the module and re-uploaded the plugins. Still no luck.

Curtis,

Can you confirm the permissions on you system/expressionengine/cache/ folder please?
What type of hosting do you have Curtis?

My cache folder is set to 777.

My hosting is with lunarpages. I don’t think that’s the problem, because it was working.

John Henry Donovan,

Just looked through the earlier posts and saw that you asked me to verify my .htaccess permissions were correct, but I’m not sure what it should be set to. What’s the correct setting?

EE must be able to write to that file. Normally that means 666 permissions or better.

It was set to 644, I changed it to 666 and tested, but still no luck.

I’m using NSM .htaccess Generator too and that was able to write to it before, as was the non-cron Blacklist Module, so I don’t think that was part of the problem.

Would it be beneficial for someone to have CP and server access? I could PM that info, if so.

Just to confirm, you can download the Blacklist manually and it gets written to .htaccess? How and where are you triggering the cron action? What template?

Yes, I can do so manually and it is written to .htaccess when I do.

I’ve tried all of the following:

{exp:cron minute="*" hour="*" plugin="cron_blacklist"}{/exp:cron}

{!-- with varied minute and hour parameters --}
{exp:cron minute="0" hour="6" plugin="cron_blacklist"}{/exp:cron}

{exp:cron minute="*" hour="*" day="1,12,15,31" month="*"}

{exp:cron minute="*" hour="*" day="*" month="*" plugin="cron_blacklist"}{/exp:cron}

I’ve tried all of these in utility/index, utility/.cron, utility/cron, utility/cron2, and site/index.

I’ve tried both embedding into the site/index as well as just putting the code in there, and I have visited the corresponding URLs at and after the times indicated by the parameters.

I’ve verified that template and tag caching are disabled and cleared the cache.

I’m seeing a similar kind of problem with my test install.. asking my colleagues if they’ve run into a similar issue.. Thanks in advance for your patience.

Ok. No problem.

Thanks for your patience. We’ll add to this thread when we know more.