Skip Navigation

[Resolved] Custom Type Training Course

This thread is resolved. Here is a description of the problem and solution.

Problem:
After logging in to Toolset I can still not access the Custom Type Training Course. It always redirects to the purchase page of the course.

Solution:
Please empty the browser's cache completely and reload the course's page after logging in again. This should resolve the issue.

This support ticket is created 5 years, 5 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
- - 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00
- - - - - - -

Supporter timezone: Asia/Ho_Chi_Minh (GMT+07:00)

This topic contains 2 replies, has 2 voices.

Last updated by Gunawan 5 years, 5 months ago.

Assisted by: Beda.

Author
Posts
#1274723

I want to access the Custom Type Training course that was announced on your blog below :
https://toolset.com/2019/05/its-here-toolsets-custom-types-training-course/

I followed the instruction on how to access this training. I login to my account already. However I did not see the "link to the course"

It kept directing me to this page below where I have to buy the course:
https://toolset.com/training-course/custom-types-from-novice-to-expert/

Please advise on how to access this training. Thank you

#1274869

This is strange, I can see the course when I log in and so can other users, it seems, however, this might be account dependent.

I will forward this issue to someone with a greater understanding of these details and will update you here as soon I have news about how to solve this.

Currently, I can only suggest trying after clearing the cache and logging in again, as it might be related to cache.

#1275803

My issue is resolved now. Beda suggested to clear the cache and it worked. Thank you!