after upgrading (which went fine), I got the following problems:
- the cron job doesn't work any more. The setcron jobs service receives the following error message "S3::getObject(, ): [InvalidAccessKeyId] The AWS Access Key Id you provided does not exist in our records". I don't have (and didn't have) any S3 service configured.
- for info when I get into the JomSocial component in the admin backend, there is an error message "Geocode was not successful for the following reason: ZERO_RESULTS"
I assign developer to this thread.
This issue is valid bug and already assigned to the developer.
To fix geo alert please you open this file administrator/components/com_community/views/community/tmpl/default.php
find this code :
alert('Geocode was not successful for the following reason: ' + status);
console.log('Geocode was not successful for the following reason: ' + status);
Oh ya i forgot the another issue, anyway this issue seems caused by conflict with JSPT configuration.. can you check it with them as well, please?
it took some times, but we did some further test with JSPT team. Here below is there answer. It doesn't appear to be a problem with JSPT. Can you please explore further?
Actually unhooking JSPT means disabling the component as well its plugins. In short, its like uninstalling component from your end.
We did this to check whether this issue is caused by JSPT or not. But, as you can see, the error didn't go away even when JSPT was unhooked. So, I think JSPT is not the root cause of this issue.
In fact, I would suggest you to once uninstall XIPT and its two plugins JSPT Community Plugin as well as JSPT System Plugin completely. Then, try to run the cron. You'll notice that this error is not resolved that concludes that its not because of JSPT configuration.
For now, I have hooked JSPT back in your system.
Please you try with the latest version 4.2.2, I hope it will be fine there.. let me know if this issue still persist
Something wrong, some of code detect you set the amazon S3.. but this is not from our configuration... but well I already fix this by hack the code, I disabled any amazon storage transfer on cron job
Thanks, now the cronjob is working.
1°) any idea where this call to amazon could come from?
2°) as it is a hack you did, should I apply it again on the next update of JS? if yes, can you let me know where/what?