Harald Ponce de Leon

Modifying the query on the product info page will not affect the search results.

@MrPhil Pitchforks and two update channels Permissions to gather pitchforks has been granted. In addition, two update release channels could be implemented: "stable" and "latest". Normal releases call out the "stable" update channel looking for updates to apply. A setting can change this to "latest" to call out the latest update channel where changes pending a normal/stable release can be pushed to.

@Jack_mcs it should work now. I also needed to update a configuration in the web server.

@Jack_mcs I forgot about updating post_max_size in the php.ini settings (upload_max_filesize was only updated previously). Give it another shot!

It should be 30MB in total including any screenshots. I'll look into the configuration again to make sure.

Perfect! That line is not in our code so I'm glad the suggestion directed you in the right place

Hi All.. v2.3.4.1 has just been pushed out with the MySQLi setup detection fix and PHP 7/MySQL 5.7 compatibility updates. This is a silent release as v2.3.5 and v2.3.6 will be pushed out soon that has these fixes already incorporated. These minor fixes were a major showstopper for new installations - far greater than I had thought of. I'm still working hard on "the big picture" and achieving my goals for this year, and sometimes need a f* tonn of pings to address these "minor" code changes. I apologize for that and urge you to keep pinging me in the future when similar showstoppers arise. v2.3.4.1 does not address bootstrap/edge, that is what v2.3.6 is for.

If you only want to show attributes A, B, C, and D on the product info page and ignore attributes E, F, and so on, you'll need to change the following query to limit the attributes returned: $attributes_query = tep_db_query("select * from " . TABLE_PRODUCTS_OPTIONS . " where language_id = '" . (int)$languages_id . "'"); to: $attributes_query = tep_db_query("select * from " . TABLE_PRODUCTS_OPTIONS . " where language_id = '" . (int)$languages_id . "' and products_options_id in (1, 2, 3, 4)"); you'll need to change the products_options_id values at the end of the query to match the attribute IDs for A, B, C, and D.

For some reason the session is being changed back on the create account page to the PHP configuration settings so instead of "osCsid" as the configured session name, the page reverts back to "PHPSESSID" for the session name. You might be calling session_start() in your create account page even though the session is automatically configured and started in includes/application_top.php. Your site has been modified so it's impossible for me to help further without having access to your server. I'm not available at the moment but you're more than welcome to post in the commercial support forum channel to receive help from others here in the community.

I see the problem you're experiencing. The session is lost when the customer visits the create account page. I'm looking further into it now..

This is what I get when I submit that form: array(13) { ["pages_id"]=> string(2) "37" ["pages_title_"]=> string(7) "fsgrstg" ["page_date_start"]=> string(0) "" ["page_date_closed"]=> string(0) "" ["sort_order"]=> string(1) "0" ["id"]=> string(1) "0" ["user_question"]=> array(1) { [0]=> string(0) "" } ["language"]=> array(1) { [0]=> string(1) "0" } ["google_choice"]=> string(1) "0" ["facebook_choice"]=> string(1) "0" ["telegram_choice"]=> string(1) "0" ["bot_response"]=> array(1) { [0]=> string(0) "" } ["bot_language"]=> array(1) { [0]=> string(1) "0" } } It looks like the fields are submitted.

It sounds like a cookie problem. File permissions shouldn't affect it but they can be checked on the Administration Tool -> Tools -> Security Directory Permissions page. Have you tried a different browser? I have experienced cookie related problems myself in the past due to my browser - after clearing the cache everything worked fine again.

Guys, the next updates will be pushed out this month. v2.3.5 and v2.3.6 will be out this month, and v2.4 will be out next month. The community bootstrap edition Gary worked on will be moved to the official v2.3.6 version.

Which update are you referring to? What was the previous version used? Did your installation work fine before the update?

Try: define('HTTP_COOKIE_DOMAIN', '.secmail.io'); define('HTTPS_COOKIE_DOMAIN', '.secmail.io'); define('HTTP_COOKIE_PATH', '/oscommerce/catalog/'); define('HTTPS_COOKIE_PATH', '/oscommerce/catalog/');