Hi,
the normal url for my cron job is rootwebaddress/index.php?option=com_community&task=cron
but then the SEO configuration of my joomla website transforms it into
rootwebaddress/fr/?option=com_community&task=cron
So Setcronjob detects an error.
is there a way to configure setcronjob to bypass that issue? (or to configure some rule in the .htaccess not to transform that specific cron request?)
regards
yves
Thank you for contacting us.
Even if Joomla! SEF is on you may still fire non-SEF URLs.
So when you configure cron job use URL provided in our documentation.
Or you use some 3rd party to create SEF URLs?
- Instead of saying: 'it's not working', explain the problem in detail.
- Screenshots with the URL visible in them and the problem marked are more than welcome.
- Tell us how to replicate the problem, we can't fix it if we can't find it.
- Make sure that your site/server meets JomSocial System Requirements
- Make sure to setup JomSocial Cron Job
- Always provide us with access details to the backend and ftp. We need it to debug problems.
- If you have a similar problem, but a solution you found isn't working, open a new thread instead of 'merging' with an existing one.
- Use the "Thank You" feature on any post that helped you
1. Edit your first post.
2. Click switch below main text field:
prntscr.com/fk3hdg
3. Provide your site details: backend URL, admin credentials and FTP:
prntscr.com/fk3hwz
4. Let us know that you provided credentials by posting in the same thread.
Usually, even with SEF on cron URL could be fired and it's working... I'll check that on your site.
- Instead of saying: 'it's not working', explain the problem in detail.
- Screenshots with the URL visible in them and the problem marked are more than welcome.
- Tell us how to replicate the problem, we can't fix it if we can't find it.
- Make sure that your site/server meets JomSocial System Requirements
- Make sure to setup JomSocial Cron Job
- Always provide us with access details to the backend and ftp. We need it to debug problems.
- If you have a similar problem, but a solution you found isn't working, open a new thread instead of 'merging' with an existing one.
- Use the "Thank You" feature on any post that helped you
- Instead of saying: 'it's not working', explain the problem in detail.
- Screenshots with the URL visible in them and the problem marked are more than welcome.
- Tell us how to replicate the problem, we can't fix it if we can't find it.
- Make sure that your site/server meets JomSocial System Requirements
- Make sure to setup JomSocial Cron Job
- Always provide us with access details to the backend and ftp. We need it to debug problems.
- If you have a similar problem, but a solution you found isn't working, open a new thread instead of 'merging' with an existing one.
- Use the "Thank You" feature on any post that helped you
I am not using S3 at all.
How to get rid off ghost S3 configuration? do you have any idea where I can remove any possible S3 indication (in JS or in other Apps or DB tables)?
I'll report this back to our developer.
He'll investigate this further.
- Instead of saying: 'it's not working', explain the problem in detail.
- Screenshots with the URL visible in them and the problem marked are more than welcome.
- Tell us how to replicate the problem, we can't fix it if we can't find it.
- Make sure that your site/server meets JomSocial System Requirements
- Make sure to setup JomSocial Cron Job
- Always provide us with access details to the backend and ftp. We need it to debug problems.
- If you have a similar problem, but a solution you found isn't working, open a new thread instead of 'merging' with an existing one.
- Use the "Thank You" feature on any post that helped you
Do safe copy of your database first.
Run this query in your database:
UPDATE `#_community_users` SET `storage` = 'file' WHERE `storage` = 's3';
Replace # with table prefix.
- Instead of saying: 'it's not working', explain the problem in detail.
- Screenshots with the URL visible in them and the problem marked are more than welcome.
- Tell us how to replicate the problem, we can't fix it if we can't find it.
- Make sure that your site/server meets JomSocial System Requirements
- Make sure to setup JomSocial Cron Job
- Always provide us with access details to the backend and ftp. We need it to debug problems.
- If you have a similar problem, but a solution you found isn't working, open a new thread instead of 'merging' with an existing one.
- Use the "Thank You" feature on any post that helped you
Hi Michal,
I run the query and replaced 26 s3 with file in the user table.
but still the same problem.
I also checked the storage field in the other _community tables but I couldn't find other s3.
I also tried again the solution in a previous ticket:
www.jomsocial.com/forum/installation/334...and-geocode?start=14
but it doesn't solve the issue either.
Do you any other idea for the cron to run?
(I added some info the credentials of the original post to access the sql tables).
regards
yves
I run the cron.php file via the scheduled task system of my own provider, and it indicates a successful run.
I don't think there may be an issue with setcronjob or in between setcronjob services and the provider because I can run other cron process for other third parties on the same website.
Just in case my problem would be then solved using my provider's scheduled tasks, how can I check that the cron is effectively doing the tasks I want. can you give q pick thing to test? :-)
regards
yves
for info, Setcronjobs has also looked at the problem.
Now there is a "more" detailed error message when your run the cron: Unknown column 'a.migrated' in 'where clause'
so you may have a script which which is looking for migrated info somewhere.
That's different issue now:
prntscr.com/hh95i2
So SQL query helped... but new issue appear :)
Check in database table _community_msg if it has "migrated" column.
If not run this query:
ALTER TABLE `#_community_msg` ADD COLUMN `migrated` INT(11);
You may check result of cron by browsing here: Backend -> Components -> JomSocial -> Monitor -> Mail queue -> Execute cron (button in upper right corner).
- Instead of saying: 'it's not working', explain the problem in detail.
- Screenshots with the URL visible in them and the problem marked are more than welcome.
- Tell us how to replicate the problem, we can't fix it if we can't find it.
- Make sure that your site/server meets JomSocial System Requirements
- Make sure to setup JomSocial Cron Job
- Always provide us with access details to the backend and ftp. We need it to debug problems.
- If you have a similar problem, but a solution you found isn't working, open a new thread instead of 'merging' with an existing one.
- Use the "Thank You" feature on any post that helped you
