Forums / Bug Reports / [Done 1.3.7] DEFINE_PAGE_NOT_FOUND_STATUS in 136 upgrade sql but not in install?

[Done 1.3.7] DEFINE_PAGE_NOT_FOUND_STATUS in 136 upgrade sql but not in install?

Locked

Started by imac on 3 Nov 2006, 7:38 AM · Views: 2,343

Results 1 to 2 of 2
This thread is locked. New replies are disabled.
3 Nov 2006, 7:38 AM
#1
imac avatar

imac

New Zenner

Join Date:
Mar 2006
Location:
Durham, UK
Posts:
78
Plugin Contributions:
0

[Done 1.3.7] DEFINE_PAGE_NOT_FOUND_STATUS in 136 upgrade sql but not in install?

Don't know if this is a bug or not.

From what I can see, the 1.3.6 upgrade sql (mysql_upgrade_zencart_135_to_136.sql) adds the admin configuration switch:```
INSERT INTO configuration (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, last_modified, date_added, use_function, set_function) values ('Define Page-Not-Found Status', 'DEFINE_PAGE_NOT_FOUND_STATUS', '1', 'Enable the Defined Page-Not-Found Text from define-pages?<br />0= Define Text OFF<br />1= Define Text ON', '25', '67', now(), now(), NULL, 'zen_cfg_select_option(array('0', '1'),');

I can't find this switch anywhere in the v1.3.6 sql install (mysql_zencart.sql) 

Have searched the forums and found this insert was recommended as a solution to 'Page-Not-Found not showing content provided via the Define Pages editor' (see Confirmed bugs and workarounds in v1.3.5 [here](http://www.zen-cart.com/forum/showpost.php?p=264364&postcount=13)  )

A small detail no doubt, but thought it might be useful to report it anyway  :smile:
3 Nov 2006, 9:16 AM
#2
drbyte avatar

drbyte

Sensei

Join Date:
Jan 2004
Posts:
63,511
Plugin Contributions:
176

Re: [Done 1.3.7] DEFINE_PAGE_NOT_FOUND_STATUS in 136 upgrade sql but not in install?

Thanks .

.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole

Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.