Exponentcms Exponent CMS → User issues

Comments and changes to this ticket

• You flagged this item as spam.
  

  Peter March 1st, 2023 @ 02:10 PM

  • Assigned user changed from “expNinja” to “dleffler”

  Sent screenshot by email. Please can you let me know if the site is usable still at this stage, before I abandon where I am with the update. Thanks. Peter.

• You flagged this item as spam.
  

  Peter March 1st, 2023 @ 02:27 PM

  Meanwhile I put the original .htaccess back with the changes that UK2 made. Now the update is working. I now see the screen showing that the selected upgrades have been done. Reloaded site and all seems well.

  I guess there is a need to preserve the existing .htaccess when an update runs, with suitable documentation if any of the Exponent entries have changed.

  Peter.

• 

  dleffler March 1st, 2023 @ 03:20 PM

  • State changed from “new” to “open”
  • Milestone set to “User issues”

  In your specific case, the host provider has added the php.ini customizations to the.htaccess instead of a php.rc file...therefore you (already) have a customized version of our.htaccess file. If you are using Git you could add it to the .gitignore, but I think you are simply extracting the package to the root folder.

• You flagged this item as spam.
  

  Peter March 1st, 2023 @ 04:33 PM

  Yeah. They are naughty but not prepared to do anything else. It kinda threw me that it fell over during the update installation. I did remember after opening the ticket that they had made those changes but hadn't expected it to stop the update. Anyway, all is well now. Maybe when the installation starts and runs the initial checks, you could check .htaccess to see if it's been changed and issue a warning?

  Peter.

• 

  dleffler March 1st, 2023 @ 04:38 PM

  • Tag set to “installer”

  While that .htaccess check might be a nice idea, unless we stored a copy of the previous .htaccess somewhere, we wouldn't be able to compare it to anything...good practice is to keep a list of 'custom' files on a site (outside of the theme). I have several of these (robots.txt, etc...) however I use Git and .gitignore.

• 

  dleffler March 1st, 2023 @ 08:08 PM

  BTW, will likely have 271patch1 out in several days...list of changes include

  v271patch1 adds these features to v271:
  - better metainfo for forms and their records - add blog dates calendar view, also greatly speed up authors and categories views (3x) - don't offer to import/export ecommerce data if ECOM is not active - allow/advertise xmlrpc editing page break to OpenLiveWriter(WP more) - moved EAAS data processing to individual modules, allows custom module integration - add form/global level unrestrict view to existing module level setting

  v271patch1 fixes these issues in v271:
  - fix xmlrpc issues w/ php v8 (errors/warnings crash output parsing) - regression fix page redirect code logic - regression fix (v220) unable to save activate module changes - fix event/show/id/x to pull the 'next' event date instead of the 1st event date - several php v8 fixes to eaas module - fix scssphp ALWAYS set timezone to UTC, created upcoming events issue

  v271patch1 updates these 3rd party libraries in v271:
  - mediaelement.js to v6.0.1 - codemirror cdn to v5.65.12 - ace editor cdn to v1.15.2 - jstree to v3.3.15 - phpxmlrpc to v4.10.1

• You flagged this item as spam.
  

  Peter March 2nd, 2023 @ 09:49 AM

  Thanks for the heads-up! Peter.

• 

  dleffler March 30th, 2023 @ 11:06 AM

  • State changed from “open” to “resolved”

  This issue was resolved by restoring the web host provided custom .htaccess file which contained all the php.ini settings needed to run Exponent.