configuration menu error

[maperr55]

HI,
Changed Admin
ran the curl test in extras. All test GOOD no failures
Changes the config.nmx_disk_cache.php to .php~
Still can not access any of the configuration menu options. ???
Mark

Also have remmed out init_nmx_disk_cache_config.php. still no go.

[lat9]

And what does 'no go' mean? Did you get another log? If so, post those contents using the "CODE" tags (the big # in the menu-bar when you write your response), remembering to xxx-out the name of your (presumed-to-be) updated admin directory's name.

[maperr55]

Hi, Sorry Thought by removing the line admin menus might work but did not.
Here is code

[21-Mar-2018 12:52:01 America/Los_Angeles] Request URI: /XXXXXXXXX/configuration.php?gID=1, IP address: 67.167.169.43
#1  trigger_error() called at [/home/mcauliffe/public_html/includes/classes/db/mysql/query_factory.php:171]
#2  queryFactory->show_error() called at [/home/mcauliffe/public_html/includes/classes/db/mysql/query_factory.php:143]
#3  queryFactory->set_error() called at [/home/mcauliffe/public_html/includes/classes/db/mysql/query_factory.php:270]
#4  queryFactory->Execute() called at [/home/mcauliffe/public_html/XXXXXXXXX/configuration.php:136]

[21-Mar-2018 12:52:01 America/Los_Angeles] PHP Fatal error:  1054:Unknown column 'configuration_tab' in 'field list' :: SELECT configuration_id, configuration_title, configuration_value, configuration_description, configuration_key, use_function, set_function, configuration_tab 
		FROM configuration
		WHERE configuration_group_id = '1'
		ORDER BY sort_order, configuration_tab ASC ==> (as called by) /home/mcauliffe/public_html/XXXXXXXXXX/configuration.php on line 136 <== in /home/mcauliffe/public_html/includes/classes/db/mysql/query_factory.php on line 171

Mark

[maperr55]

Hi, Sorry Thought by removing the line admin menus might work but did not.
Here is code

[21-Mar-2018 12:52:01 America/Los_Angeles] Request URI: /XXXXXXXXX/configuration.php?gID=1, IP address: 67.167.169.43
#1  trigger_error() called at [/home/mcauliffe/public_html/includes/classes/db/mysql/query_factory.php:171]
#2  queryFactory->show_error() called at [/home/mcauliffe/public_html/includes/classes/db/mysql/query_factory.php:143]
#3  queryFactory->set_error() called at [/home/mcauliffe/public_html/includes/classes/db/mysql/query_factory.php:270]
#4  queryFactory->Execute() called at [/home/mcauliffe/public_html/XXXXXXXXX/configuration.php:136]

[21-Mar-2018 12:52:01 America/Los_Angeles] PHP Fatal error:  1054:Unknown column 'configuration_tab' in 'field list' :: SELECT configuration_id, configuration_title, configuration_value, configuration_description, configuration_key, use_function, set_function, configuration_tab 
		FROM configuration
		WHERE configuration_group_id = '1'
		ORDER BY sort_order, configuration_tab ASC ==> (as called by) /home/mcauliffe/public_html/XXXXXXXXXX/configuration.php on line 136 <== in /home/mcauliffe/public_html/includes/classes/db/mysql/query_factory.php on line 171

Mark

HI, this is the log info not code.

[mc12345678]

Hi, Sorry Thought by removing the line admin menus might work but did not.
Here is code

[21-Mar-2018 12:52:01 America/Los_Angeles] Request URI: /XXXXXXXXX/configuration.php?gID=1, IP address: 67.167.169.43
#1  trigger_error() called at [/home/mcauliffe/public_html/includes/classes/db/mysql/query_factory.php:171]
#2  queryFactory->show_error() called at [/home/mcauliffe/public_html/includes/classes/db/mysql/query_factory.php:143]
#3  queryFactory->set_error() called at [/home/mcauliffe/public_html/includes/classes/db/mysql/query_factory.php:270]
#4  queryFactory->Execute() called at [/home/mcauliffe/public_html/XXXXXXXXX/configuration.php:136]

[21-Mar-2018 12:52:01 America/Los_Angeles] PHP Fatal error:   1054:Unknown column 'configuration_tab' in 'field list' :: SELECT  configuration_id, configuration_title, configuration_value,  configuration_description, configuration_key, use_function,  set_function, configuration_tab 
        FROM configuration
        WHERE configuration_group_id = '1'
        ORDER BY sort_order, configuration_tab ASC ==> (as called by)  /home/mcauliffe/public_html/XXXXXXXXXX/configuration.php on line 136  <== in  /home/mcauliffe/public_html/includes/classes/db/mysql/query_factory.php  on line 171

Mark

Looks like the admin/configuration.php file has/had been modified to support the same code (plugin/template?) as previously identified. Ie. in building the software for this install, changes have been made that are not related to either of the two mods that have been identified. lat9 suggested that perhaps more than one template had been attempted before deciding on using the responsive all business template. If that were the case or any other attempted mod install was performed to the fresh 1.5.5f install, then the removal of the same mod(s) was not complete (ie. may have removed/undone some sql related work, but some portion of the software remains).

The easy action to describe within the forum is to rebuild the software of the site to contain just the core files and the two mods described (plus any "personalizations" that have been made). The more effective path would be to possibly do that anyways in another location and then remove any files/code from the live site that does not belong when comparing the live site with the rebuilt one. A third alternative is to evaluate the differences in the current site to a vanilla install and then "remove" any file that is not associated with the default install and the files from the two mods. There are ways to do this relatively quickly (Beyond Compare or other such tools that support remote file comparison which there is at least one open source program that supports that.) By removal I mean taking action similar to previously described of changing the suffix (extension) of such file(s) to not be .php with a plan to remove the file(s) once resolved.

Ultimately, because we are talking about your live site, the suggested path is to first reproduce the entire site somewhere, then take action to restore the copy of the site. Once successful, then reproduce those actions with the actual live site so that although the configuration area is not currently reachable, at least the site is still productive capable.

[maperr55]

Looks like the admin/configuration.php file has/had been modified to support the same code (plugin/template?) as previously identified. Ie. in building the software for this install, changes have been made that are not related to either of the two mods that have been identified. lat9 suggested that perhaps more than one template had been attempted before deciding on using the responsive all business template. If that were the case or any other attempted mod install was performed to the fresh 1.5.5f install, then the removal of the same mod(s) was not complete (ie. may have removed/undone some sql related work, but some portion of the software remains).

The easy action to describe within the forum is to rebuild the software of the site to contain just the core files and the two mods described (plus any "personalizations" that have been made). The more effective path would be to possibly do that anyways in another location and then remove any files/code from the live site that does not belong when comparing the live site with the rebuilt one. A third alternative is to evaluate the differences in the current site to a vanilla install and then "remove" any file that is not associated with the default install and the files from the two mods. There are ways to do this relatively quickly (Beyond Compare or other such tools that support remote file comparison which there is at least one open source program that supports that.) By removal I mean taking action similar to previously described of changing the suffix (extension) of such file(s) to not be .php with a plan to remove the file(s) once resolved.

Ultimately, because we are talking about your live site, the suggested path is to first reproduce the entire site somewhere, then take action to restore the copy of the site. Once successful, then reproduce those actions with the actual live site so that although the configuration area is not currently reachable, at least the site is still productive capable.

Hi,
Thank you for the brain thought to read that error. It sound pretty obvious that the first install of the cart and other templates left entries in the DB. The reinstall of the cart though it was a clean reinstall, their were DB entries that were not over written. The site have only been up a few days and most work stopped to resolve issues. I think at this point I believe the wisest thing is blow it all away and this time a brand new DB. No left overs that way. Only lose a few hours that way.
First time I have had this much issue installing a cart and I've done more than a dozen. But the basic install worked with no problem.
Thanks for your time.
Mark

[mc12345678]

Hi,
Thank you for the brain thought to read that error. It sound pretty obvious that the first install of the cart and other templates left entries in the DB. The reinstall of the cart though it was a clean reinstall, their were DB entries that were not over written. The site have only been up a few days and most work stopped to resolve issues. I think at this point I believe the wisest thing is blow it all away and this time a brand new DB. No left overs that way. Only lose a few hours that way.
First time I have had this much issue installing a cart and I've done more than a dozen. But the basic install worked with no problem.
Thanks for your time.
Mark

Well, even though the database may have some incorrect fields, it can and should be usable as is. The issue is the software trying to access it. Ie, with a brand new fileset that only tries to access the fields that are expected to exist, the worst thing is that there is/may be some database bloat which could be addressed through other means.

Reason I bring this up even if the stated actions have been performed is that existing new history can be retained while the code is corrected to do what is right...

The software drives the operations, the database retains the status.