X-Cart forums

[ITVV]

Hi,

I must confess that I am really confused as to why 4.6.? is been ignored

There must be tons of sites running 4.6.?

Why abandon a relatively new version of x-cart but support a real out of date 4.0.? version

Answers on a postcard please!!!

Kind regards

ITVV

[simetria]

Originally Posted by chamberinternet

I think the module is designed for the 4.7.x branch :-/

Yeah, but in the post above Anna mentions that the version 4.7.x of the module can be "Adapted" for a 4.6.x. Just wondering if anyone has done it. She lists some things that need to be changed to fit the version you're adapting to, but by the time we figure this out, the 25th has come and gone lol.

-S

[pauldodman]

Nothing is really supported other than 4.7.x.
Anything else, and it's just - yeah, good luck with that!

Anyway, for any other version, start by editing:
install-eugdpr.php

And find around line #45:
define('COMPATIBLE_VERSION', '4.7.5');

And just change the version to your version, and you should be able to make some progress.

You don't have to do it by install though, you can do it manually.

[ITVV]

It could just be me but I am totally confused

So if you have an ANCIENT version of xcart you can use eu-gdpr-dev-pack-4.0.x-4.5.x.tgz package.

However if you are on 4.5.1 or 4.6.? you have to hand-roll the solution

How come 4.5.1 and 4.6.? are the odd ones out

Perhaps its just me that's not understanding this?

I just do not get the logic - why would you leave out the last two packages but support the ancient versions?

Perhaps is to try and force people to upgrade to 4.7.? and pay the annual maintenance fee? There you go - I answered my own question. That's why 4.5.1 and 4.6.? have been ignored

Go figure the logic in that business model.

Regards

ITVV

[simetria]

I agree, seems really confusing as to why 4.5.1 through 4.6.x are left out of the mix.
At least a simple guide on how to adapt 4.7.0 module to fit 4.5.1 through 4.6.x.

-S

[pauldodman]

No, you are making it sound like if you have an ancient version, you have the same easy, off the shelf solution that you do for 4.7.
You don't.

If you have an ancient version, you use that pack as the basis of the process - you still have to do manual development.
And if you have 4.5.1 to 4.6.x then you use the 4.7 pack as the basis.

[ITVV]

@pauldodman,

I must admit that I have not looked at the packs yet. All I did was read what the press release said and became instantly confused.

Not bothered about an 'auto install' I am happy to manually patch.

But what is confusing for me, at this stage, is why I would have to hack another versions upgrade pack?

Is the press release ambiguous?

Regards

ITVV

[simetria]

ITVV what does manual patching actually intel? Sorting out the files in their respective directories based on the structure inside the module download? Applying the db/sql files from the module via the Tools/Patches menu in the backend?

[Triple A Racing]

Originally Posted by ITVV

....Is the press release ambiguous?

The XC Marketing Department do have the odd claim to fame...
“...If you don't read the newspaper, you're uninformed. If you read the newspaper, you're mis-informed...” - Mark Twain

[ITVV]

@simetria

ITVV what does manual patching actually intel? Sorting out the files in their respective directories based on the structure inside the module download? Applying the db/sql files from the module via the Tools/Patches menu in the backend?

Yes and manual patching of files / templates to reference new files / changes.

Kind regards

ITVV