Harald Ponce de Leon

Hi All.. A quick progress update regarding what we've been working on recently. A new Community Team is being formed to help moderate community submitted content and to help with community relations and issues. This not only helps the developers in the team to focus more on code development and less on moderation, but also broadens the voice in the team when community related issues arise and are addressed. This new approach to the team is being ironed out and we'll be glad to invite more active users in the community to help out once everything is running smoothly again. For the curious, those we have initially invited can be seen on the forum staff page. An internal build of v2.3.5 has been in testing and this weekend will be spent fixing the known issues. A majority of reported issues and pull requests at Github have been addressed and will also make their way into v2.3.6 (the Community Bootstrap edition). These releases are planned to be the last in the v2.3.x release series to place all resources on v2.4/v3.0. Accommodations will be made if the community wish to continue working on v2.3.6 for future v2.3.x releases. More information about this will be announced with the releases. The next test builds will be made available to Ambassadors for a wider testing audience. Both releases will be officially pushed out this month. The forum software has been updated to the latest release series and introduces a new Clubs section to the forum. We've moved our partner announcements forum channels to the Clubs section where our partners can customize their own club sections further with logos and additional discussion channels. We're planning on adding multilingual Clubs in the near future, and also community requested clubs (eg, for community release editions). The upgrade of the forum software version was originally postponed due to changes made with user accounts and the integration we have with our main website. This also plays a role with the marketplace integration in v2.4 where user accounts are required. An online update for 2.4 will be pushed out soon to test the marketplace integration and user account logins/creations with. Release dates for v2.4 will be provided when the marketplace integration online update has been pushed out. Two new websites were planned to be launched in Q4 but are being pushed back to Q1 2018 to push our next releases out first. The new websites are for a proper commercial support inquiry / job marketplace website (to replace the not-so-user-friendly forum channel here in the forums), and a new user profile website (for Ambassadors) to highlight ones profile across all of our websites (submissions from our forums, live sites, and apps marketplace websites), with the focus on the person behind the screen name. Hope everyone has a great festive season!

I don't know if expose_php could fix the problem - this setting can only be disabled in the php.ini file and not in a htaccess file. This is why only your hosting provider can change that value. This is noted in the PHP documentation: http://php.net/manual/en/ini.core.php I don't know. If it works for you it may be an alternative solution.

Yep, if you move that file to your admin directory, the admin path will be added to the email headers. This is something only your hosting provider can fix. It would be best to send them an inquiry on how to get it fixed. The test code is using the native PHP mail() function and does not contain any osCommerce code or configuration.

@mhsuffolk, create a file on your webserver and copy the following code to it, replacing your@email_address with your working email address. Request the file with your browser to send a test email. If the php filename is still being shown in the email headers, you will need to contact your hosting provider to get them to fix it for you on their end. <?php mail('your@email_address', 'Test Subject', 'Test Message'); echo 'Sent!'; ?>

Can you please confirm that the mail.add_x_header value is set to Off on the Admin -> Tools -> Server Info page. The expose_php value should also be set to Off.

v2.3.4.1 is a hotfix release that addresses compatibility with PHP 7 and MySQL 5.7. This is the changelog for the release: * Improve detection of MySQLi during setup. * Update session handler functions to return correct return value types. * Ignore E_DEPRECATED PHP notices. * Set empty MySQL sql_mode for compatibility across MySQL versions.

This is strange as the minimum cURL and OpenSSL version requirements for TLS v1.2 are supported (judging by your screenshots). Do test transactions work with PayPal with "Verify SSL" set to True and "SSL Version" set to either Default or TLS v1.2? It might just be the test connection script failing under your environment.

Just to clarify that statement, the SSL certificate used on the web server (to serve https) has nothing to do with the ssl libraries curl have been compiled with into PHP. Optimally, Verify SSL should be left to True. Try setting the SSL Version from Default to TLS v1.2.

The requirement that the site must be powered by osCommerce is no longer in place with the new Live Sites website. This is due to the many forks of osCommerce available and not wanting to spend resources policing each submission. Each submission is processed in the background though to make sure a valid website has been submitted. The listings now serve as an inspiration of what can be achieved in e-commerce, websites (v3 framework), user interface design, and technology.

Right now it's possible for the author to edit the short and main description of their submission where a note can be added. It's also possible for the author to allow others to upload updates to the submission (either everyone or specific users) so others can continue development. In the near future it will be possible for authors to remove their submissions. How should the flag work with that in mind? Should a flagged submission allow updates to be uploaded or should it remain in a permanent locked state? Should flagged submissions show in the listing and search results or be hidden and only accessible via a direct url? Should an extra warning be shown in the download window? @raiwa your feedback on this would be great!

Hi All.. Both v2.3.5 and v2.3.6 were planend to be released today (end of August) however a few more days is needed. This topic will be updated on the weekend with the date next week when the releases will be pushed out. Kind regards,

If you're already running on v2.3.4 without any issues, there is no need to update to v2.3.4.1. It would be better to update to v2.3.5 to apply the latest security fixes, compatibility fixes, and bug fixes. You will also have the option to update to v2.3.6 when you're ready to move to the bootstrap series. v2.3.5 will not break compatibility with existing addons - it's a maintenance release that will finalize the v2.3.4 release series and is planned to be the last release of this series. v2.3.6 may break compatibility with existing v2.3.4 addons due to moving to bootstrap. The 2.3.6 version label will be added to the Apps Marketplace once it's released so updated addons and Apps can be clearly labelled.

The "AJAX Attribute Manager BS" submission is now linked to the "AJAX Attribute Manager support" support topic.

@raiwa done!