- Posts: 3722
COMMUNITY FORUM
3.8 update
- william white
- Topic Author
- Offline
- Platinum Member
Less
More
7 years 2 months ago #164293
by william white
3.8 update was created by william white
Please do the following when updating
BACKUP YOUR SITE
Update your K2 to version 2.8 and test
Visit downloads.joomla.org/technical-requirements and check your system requirements.
In your Administrator go to Extensions/Manage/Update - update all your extensions you can and test each one before proceeding to the next
Set error reporting to Maximum in Global configuration and save
Use the Components/Update to update your site to 3.8
Test your site and your components
If you have errors try to disable the plugin or component that is causing the problem/ report it to the developer when you are sure that you have found culprit
This could save a lot of misery and time - especially the first and most important duty of a webmaster - Backup Your Site
BACKUP YOUR SITE
Update your K2 to version 2.8 and test
Visit downloads.joomla.org/technical-requirements and check your system requirements.
In your Administrator go to Extensions/Manage/Update - update all your extensions you can and test each one before proceeding to the next
Set error reporting to Maximum in Global configuration and save
Use the Components/Update to update your site to 3.8
Test your site and your components
If you have errors try to disable the plugin or component that is causing the problem/ report it to the developer when you are sure that you have found culprit
This could save a lot of misery and time - especially the first and most important duty of a webmaster - Backup Your Site
The topic has been locked.
- ha linh
- Offline
- New Member
7 years 2 months ago #164301
by ha linh
Replied by ha linh on topic 3.8 update
Thanks for sharing the tutorial, Good health!
The topic has been locked.
- kasra khoshkhooy
- Offline
- New Member
7 years 2 months ago #164306
by kasra khoshkhooy
Replied by kasra khoshkhooy on topic 3.8 update
thx for sharing
The topic has been locked.
- Krikor Boghossian
- Offline
- Platinum Member
Less
More
- Posts: 15920
7 years 2 months ago #164316
by Krikor Boghossian
JoomlaWorks Support Team
---
Please search the forum before posting a new topic :)
Replied by Krikor Boghossian on topic 3.8 update
Nice one William :)
JoomlaWorks Support Team
---
Please search the forum before posting a new topic :)
The topic has been locked.
- guanio ramon
- Offline
- New Member
7 years 2 months ago #164380
by guanio ramon
Developer joomunited
Replied by guanio ramon on topic 3.8 update
hi william white,
I hope you are doing well.
I am the developer of my map locations and created this integration.
When we have tested the solution of k2 everywhere its working perfectly.
even we have over 1500 active customer using k2 with my map location and none of them reported this issue.
Can you please help me out the way so I can recreate the issue and try to solve it asap.
I hope you are doing well.
I am the developer of my map locations and created this integration.
When we have tested the solution of k2 everywhere its working perfectly.
even we have over 1500 active customer using k2 with my map location and none of them reported this issue.
Can you please help me out the way so I can recreate the issue and try to solve it asap.
Developer joomunited
The topic has been locked.
- william white
- Topic Author
- Offline
- Platinum Member
Less
More
- Posts: 3722
7 years 2 months ago #164386
by william white
Replied by william white on topic 3.8 update
Thanks for your reply here and also in the ticket i created.
I have deleted the post that mentions your plugin here in the forum and will be in touch via the ticket i created as it seems that this issue may have been reported incorrectly ( or maby I could just have a combination of components and plugins that cause this)
I am glad to hear that there are no other complaints and will be in touch asap in your ticket system.
I have deleted the post that mentions your plugin here in the forum and will be in touch via the ticket i created as it seems that this issue may have been reported incorrectly ( or maby I could just have a combination of components and plugins that cause this)
I am glad to hear that there are no other complaints and will be in touch asap in your ticket system.
The topic has been locked.