Upgraded live site after having tested 2.99.0 beta on test install. Following are observations (which may or may not be helpful and applicable to other installations):
Post upgrade, the last_build_date global showed a date in 2004. Applying Repair DB and rebuilding corrected the same but introduced following issue:
Still To Test:
All Mailing related issues.
Suggestions:
Shall add on whatever comes to mind ... not throwing in my towel as yet
All in all ... Good Job Done ...
[EDIT]
Ignore the typos ... there could be many
[EDIT]
Thanks
HyTC
==================================
Mail Me If Contacting Privately Is That Necessary.
==================================
- Upgrade was smooth thru the installer. No major glitches (except for one issue related to and detailed under "Unresolved Probelms")
- luna modification pretty OK even for a CSS beginer like us. That's the fastest way to switchover ... new layouts can come later but this is more feasible than trying to make 2x templates to work with Glinks 3 Features...
- 2X template compatibility by and large OK except for that title linked error (invalid tag) on Cool/New pages. Not a major issue as immediately changed over to modified luna after upgrading
- Plugins used (Andy's contact page and recommendit work fine ... though the email part needed modification as due to CSS the received mails were losing all formatting.
- Globals all work fine except for one which is detailed later.
- Add Link/Modify Link Works fine
- URL validation works fine during Add Link (except for one URL which has always been giving probelm and could not connect error -- right from 2X version also. This is a cnamed entry and always gives could not connect error) which is the New Addition.
- BookMark/Newletter user interface works fine.
- <%page_id%> is wonderful, Adds a lot of flexibility and also makes the tough balancing act between the rhs/lhs column and content area balancing pretty much easy.
- Abandoned HTMLArea ... due to issues of Detailed Page Data with validator.w3.org ... it's going to be a painful ordeal validating each Detailed page and making it compliant but that's what separates Admins from the rest. Not too sure if we will ever include that at least in near future.
- Multiple GT products under mod_perl and found issues with table update from admin as long as Gcom was under mod_perl. softlinking Community GT libs to Glinks GT lib resolved the issue.
- Updates work fine after the initial "INVALID License" glitch.
Post upgrade, the last_build_date global showed a date in 2004. Applying Repair DB and rebuilding corrected the same but introduced following issue:
- The "NEW" status on Home Page is Never Displayed. The same however is fine on Category, Detailed And Cool pages.
- latest_n by category global which worked fine (intended to display Latest N listings Category Downwards when called on category.html) in 2X breaks in Glinks 3. It just displays "In Category" and not "Category Downwards"
Still To Test:
All Mailing related issues.
Suggestions:
- A separate installation location for GT libs thru the installer with each product installer also asking for the path to GT libs (if installing a second product) or setting it up if installing the "First" GT product, and doing a ln -s thru the installation process. This would make maint so very easy. Currently if it is doen manually, i am not sure how installer would behave upon upgrades to ln -s .../.../.../GT GT thing.
- A complete rethinking on the way the "Review" system currently works. it is open to gross abuse in certain setup config (ie Admin sets it to Auth Not Needed to Submit reviews)
- GT gets a core team of beta testers picked up from their client list (not that i am hinting that we are prepared to be doing beta testing ... we already have been doing it anyway)
- Include Ready To Use Globals as picked up from the threads which almost get lost into oblivion on the forums... it's always not easy to search.
- Remove plugins from the Plugins Download Area which have become reduntant in view of feature sets introduced in Glinks 3
- MTA less communication between Admin and End User. Though this has been rejected but still suggesting this.
- Ability for the users to update passwords, though this could become reduntant with community route.
- Remote Search is again a thing which is half complete ... so a completed XML Search .... not just the ability to pass in XML=1 to query.
Shall add on whatever comes to mind ... not throwing in my towel as yet
All in all ... Good Job Done ...
[EDIT]
Ignore the typos ... there could be many
[EDIT]
Thanks
HyTC
==================================
Mail Me If Contacting Privately Is That Necessary.
==================================