X-Cart forums

[cflsystems]

Originally Posted by carpeperdiem

Roll Call from our leading mod developers, please?

I never used smarty php tag for the above reasons. Also never used any direct php modifiers in templates

[aim]

Originally Posted by cflsystems

I never used smarty php tag for the above reasons. Also never used any direct php modifiers in templates

This is the professional style.

[cherie]

Using php modifiers is normal. That's why it's in XMonitoring. Any developer can add the same line to their config. The key to this security is to prevent just anyone from adding an unauthorized php modifier to a tpl which is good practice.

[Carzilla]

After updating, I'm getting this message:

Assertion Failed: File 'httpdocs/devshop/include/classes/class.XCSignature.php':Line '78'
Code '$result /* XCSignature::checkSignature: checkSignature was failed*/'
Please post a new ticket here https://bugtracker.qtmsoft.com
Please, attach the var/log/x-errors_assertion-130221.php file to the ticket.

Any idea how to solve this?

[aim]

Originally Posted by aim

Thank you for your suggestions.

I have uploaded the new upgrade packs with the following changes.

*A new 'Stop the upgrade process in case of problems related to major files like func.core.php. Uncheck this option to proceed anyway (NOT RECOMMENDED)' checkbox is added (enabled by default)

*The "Tick here to continue upgrading regardless of the found problems" checkbox is renamed to
Warning:The initial check shows that some of the files in your installation may not be patched cleanly because some of the hunks (blocks of code changes) cannot be applied.Allow Patch/Upgrade center to try and patch the files the best it can? (enabled by default)

*Patch/Upgrade center tries to apply the patch.sql and after-path files anyway.

*patch.sql is applied in 'force' mode. It does not stop on SQL error.

Please, note the changes are related to the 4.5.?-4.5.5 upgrade packs only.

[aim]

Originally Posted by Carzilla

After updating, I'm getting this message:

Assertion Failed: File 'httpdocs/devshop/include/classes/class.XCSignature.php':Line '78'
Code '$result /* XCSignature::checkSignature: checkSignature was failed*/'
Please post a new ticket here https://bugtracker.qtmsoft.com
Please, attach the var/log/x-errors_assertion-130221.php file to the ticket.

Any idea how to solve this?

It seems your upgrade process was not properly completed.

Please, provide us with the
upgrade/4.5.4-4.5.5/patch.log
var/log/x-errors_sql-1302*.php
files

[Carzilla]

Originally Posted by aim

It seems your upgrade process was not properly completed.

Please, provide us with the
upgrade/4.5.4-4.5.5/patch.log
var/log/x-errors_sql-1302*.php
files

Hello,

Thanks for your reply. I sadly don't have any patch.log in my upgrade map (I'm trying to upgrade from 4.5.3, so I presume it should've been in 4.5.3-4.5.5).

Is there any way (for example a .sql file) at which I can force the database back to a 'clean' 4.5.3 state so I can try again? Or is the smartest method to solve this to just do a clean install of 4.5.5 and copy my custom skin in it?

Attached is the assertion file it suggest me to send.

Thanks for the help.

[aim]

Originally Posted by Carzilla

Hello,

Thanks for your reply. I sadly don't have any patch.log in my upgrade map (I'm trying to upgrade from 4.5.3, so I presume it should've been in 4.5.3-4.5.5).

Is there any way (for example a .sql file) at which I can force the database back to a 'clean' 4.5.3 state so I can try again? Or is the smartest method to solve this to just do a clean install of 4.5.5 and copy my custom skin in it?

Attached is the assertion file it suggest me to send.

Thanks for the help.

How many providers and admins do you have ?
Do you use the Social Login module?
Do you use a separate folder for your skin?
Do you have the upgrade/4.5.3-4.5.5/patch.log file ?
How many 'Could not patch' errors have you received ?

[Carzilla]

Originally Posted by aim

How many providers and admins do you have ?
Do you use the Social Login module?
Do you use a separate folder for your skin?
Do you have the upgrade/4.5.3-4.5.5/patch.log file ?
How many 'Could not patch' errors have you received ?

No providers, just one admin - me.
We don't use the social login module.
We do use a separate folder for our skin.
I don't have that .log file. After patching it 'crashes' on the result page, turns blank.
There were some (╠ 5-6) errors, all on tpl files.

Thanks again!

[aim]

Originally Posted by Carzilla

No providers, just one admin - me.
We don't use the social login module.
We do use a separate folder for our skin.
I don't have that .log file. After patching it 'crashes' on the result page, turns blank.
There were some (╠ 5-6) errors, all on tpl files.

Thanks again!

It is strange, the patch.log file should be created anyway.

OK
The possible solution is

1 Run the upgrade/4.5.3-4.5.5/patch.sql file in the 'force' mode again

2 Run the SQL query
delete from xcart_config where name in ('allowed_ips', 'ip_register_codes');

3 Disable the CHECK_CONFIG_INTEGRITY CHECK_CUSTOMERS_INTEGRITY in the config.php file

4 Enter to the admin area

5 Enable the X-Payments Connector module

6 Check all the options and click the 'Update' button on the pages
http://xcart2-54.crtdev.local/~aim/xcart_4_5_x/admin/configuration.php?option=Company
http://xcart2-54.crtdev.local/~aim/xcart_4_5_x/admin/configuration.php?option=XPayments_Connector
http://xcart2-54.crtdev.local/~aim/xcart_4_5_x/admin/configuration.php?option=Email
http://xcart2-54.crtdev.local/~aim/xcart_4_5_x/admin/configuration.php?option=Email_Note
http://xcart2-54.crtdev.local/~aim/xcart_4_5_x/admin/configuration.php?option=Security

7 Open an each admin/provider profile and click the 'Update' button.

8 Disable the X-Payments Connector module

9 Enable the CHECK_CONFIG_INTEGRITY CHECK_CUSTOMERS_INTEGRITY in the config.php

10 You have to re-generate the Blowfish and security keys using the default 'Re-generate Blowfish encryption key' feature from the admin area.
Please, do not ignore this step!