Hi Thorsten,
I have gone through the upgrade steps again in a sandpit but I still cannot access the articles once I have upgraded.
Please let me know if you are still interested in looking at the setup and I will arrange access to the sandpit.
By the way, it looks as if the problem might be with ...
Search found 3 matches
- Wed Jul 23, 2014 9:59 am
- Forum: General discussions
- Topic: Articles inaccessible after upgrading from 2.6.8 to 2.8.10
- Replies: 4
- Views: 3695
- Thu Jul 10, 2014 2:11 pm
- Forum: General discussions
- Topic: Articles inaccessible after upgrading from 2.6.8 to 2.8.10
- Replies: 4
- Views: 3695
Re: Articles inaccessible after upgrading from 2.6.8 to 2.8.
Hi Thorsten,
Thanks for responding.
I have had to roll back to 2.6.8, but I can reproduce it in a sandpit and let you take a look. The FAQ runs in a intranet, but I can arrange remote access to the sandpit via something like Webex.
I am thinking that my upgrade steps may have been not correct. I ...
Thanks for responding.
I have had to roll back to 2.6.8, but I can reproduce it in a sandpit and let you take a look. The FAQ runs in a intranet, but I can arrange remote access to the sandpit via something like Webex.
I am thinking that my upgrade steps may have been not correct. I ...
- Wed Jul 09, 2014 2:28 pm
- Forum: General discussions
- Topic: Articles inaccessible after upgrading from 2.6.8 to 2.8.10
- Replies: 4
- Views: 3695
Articles inaccessible after upgrading from 2.6.8 to 2.8.10
Hi guys,
I have just upgraded my install from 2.6.8 to 2.8.10. The upgrade seemed successful. However when I connect to the FAQ, I see the news items and links to the most popular, latest and sticky articles but I cannot view any of the articles. When I click on a link, I get "Page cannot be ...
I have just upgraded my install from 2.6.8 to 2.8.10. The upgrade seemed successful. However when I connect to the FAQ, I see the news items and links to the most popular, latest and sticky articles but I cannot view any of the articles. When I click on a link, I get "Page cannot be ...