Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Export Task not working #101

Closed
bbaermann opened this issue Jul 19, 2022 · 4 comments · Fixed by #102
Closed

Export Task not working #101

bbaermann opened this issue Jul 19, 2022 · 4 comments · Fixed by #102
Labels

Comments

@bbaermann
Copy link
Contributor

After creating an nearly empty task, and trying to export it, Browser shows:

"Not Found
The requested URL was not found on this server."

The URL in my case was: http://localhost/civicrm/sqltasks/export?id=1

This behaviour is with latest master branch.

@bbaermann bbaermann added the bug label Jul 19, 2022
@pfigel
Copy link
Collaborator

pfigel commented Jul 19, 2022

Does this still happen if you open /civicrm/menu/rebuild first?

I suspect we just need to add a cache flush in an upgrader somewhere.

@bbaermann
Copy link
Contributor Author

still happening after rebuild.

The correct URL should be http://localhost/test/civicrm/sqltasks/export?id=1

so i suppose it has to do with the way i build my testing environment here and it is maybe not a sqltask bug at all. I will look into it.

pfigel added a commit to greenpeace-cee/de.systopia.sqltasks that referenced this issue Jul 19, 2022
@pfigel
Copy link
Collaborator

pfigel commented Jul 19, 2022

Ah, I see what's happening here - I used an absolute URL instead of going through crmUrl. 😅

#102 should resolve this. Thanks for reporting!

@bbaermann
Copy link
Contributor Author

Great, Thanks!

bbaermann added a commit that referenced this issue Jul 20, 2022
Fixes [#101] Export Task not working 
Fix export URL not being generate via crmUrl
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants