GIJOE,

Tying to figure out this upgrading issue:

Main site is not upgrading completely or not at all =- templates and joints are not showing up. Standard upgrading procedures.

Test site is kinda upgrading. Several versions were installed and some updated to .56a, others not.

Test site upgraded folders show new pipe joints like reassign-truncate, but do not show any new templates like main_cliplist.html.

And strangely, folders that were NOT upgraded show the new pipe joints (in pipe admin), and still none of the new templates.

Is this because I have freshly installed a version of .56 to this test setup? IE no upgrade? And then these functions/options are finally showing up (on all d3pipes folders)?

In other words an upgrade failure is occurring and the only way to get new functions is to install a fresh copy in a new folder? (and then they are available to ALL d3pipes folders/pipes) Although, this does not solve the missing templates issue - which is just as big an issue.

I've setup the test site (same server) to confirm issues and not bring up stuff unnecessarily - I think something is amiss here.

I am using PHP5 - could this be causing an upgrading issue, yet not a working issue?

All of my previous issues are on hold (date transformation (malformed date), entry listing order and the ability to DELETE an entry, because I cannot confirm (don't believe) that the upgraded files and templates that would fix those issues, are being used by the system.

2.0.16 and PHP5, .55 of ALTSYS

Thanks.

These must be some kind of mistakes.

- templates problem
patch and clear template cache.

- Joints problem
Perhaps, you don't upload the new archive into right place.


Do you understand the meanings/differences of XOOPS_ROOT_PATH and XOOPS_TRUST_PATH?

Thanks for getting back to me,

I'm tending to think now thatit's a resource.db type problem or some sort. I had the it patched, but it may have been the xoops.org patch and not yours.

I've downloaded your latest 56a and the resource.db patch and am going to try again with a new test system.

I should probably try/use 2.0.17, but the production system is 2.0.16 - so, that's what I'll use.

Thanks.

Found the problem - it was a frankworks issue. Somehow, the frameworks 1.2 folder got overwritten with an older 1.1 version.

Thanks for all your help.

framework?

I believe there is no framework damages d3pipes or other modules.
If it exists, the framework should be called as "Hack".