<?xml version="1.0" encoding="UTF-8"?>    <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
      <channel>
        <title>CMSB v3.71 Released (Jun 18) -Help Tooltips &amp;amp; Upload Features</title>
        <link>https://interactivetools.com/forum/forum-posts.php?CMSB-v3_71-Released-Jun-18--Help-Tooltips-Upload-Features-82822</link>
        <description></description>
        <pubDate>Wed, 11 Nov 2026 15:31:13 -0700</pubDate>
        <language>en-us</language>
        <atom:link href="https://interactivetools.com/forum/forum-posts.php?rss=1&amp;CMSB-v3_71-Released-Jun-18--Help-Tooltips-Upload-Features-82822" rel="self" type="application/rss+xml" />

                <item>
          <title>MAJOR ISSUE TRYING TO CREATE/SAVE EMAIL TEMPLATES with CMSB v3.71 Released (Jun 18) </title>
          <link>https://interactivetools.com/forum/forum-posts.php?postNum=2247462#post2247462</link>
          <description><![CDATA[<p>Hi All, </p>
<p>For anyone having issues saving email templates in v3.71, I've attached a patched file to this thread.  </p>
<p>Here's how to fix it: </p>
<ul>
<li>Confirm you're running v3.71, this patched file is only for that version.</li>
<li>Rename /cmsb/lib/menus/_email_templates/actionHandler.php to actionHandler.php.backup</li>
<li>Upload the attached file to /cmsb/lib/menus/_email_templates/actionHandler.php to actionHandler.php</li>
</ul>
<p>Hope that helps, if you run into any other issues just let us know. </p>
<p>Thanks!</p>]]></description>
          <pubDate>Wed, 28 Aug 2024 14:01:50 -0700</pubDate>
          <guid isPermaLink="true">forum-posts.php?postNum=2247462#post2247462</guid>
        </item>
                <item>
          <title>MAJOR ISSUE TRYING TO CREATE/SAVE EMAIL TEMPLATES with CMSB v3.71 Released (Jun 18) </title>
          <link>https://interactivetools.com/forum/forum-posts.php?postNum=2247456#post2247456</link>
          <description><![CDATA[<p>I am having the same, or very similar, error.  When I try to save, or resave with changes, I get a pop up for errors that has a bunch of html code...kind of looks like a bad wysiwyg experience.  I will include two screenshots here.</p>
<p>I am using the newest cmsb version for live servers (3.71).  The problem occurs in any browser (Ffx, Chrome, Edge, Opera) and while changing or adding any field after an initial creation. I have also logged off, cleared all temp/cache/cookies, etc. and rebooted my PC - but still get the gobbledey-gee popup and no new changes are saved.  The system WILL retain whatever was previously successfully saved. </p>
<p>It's the last area I have to install for this customer and this one issue is holding the site back.  Thank you kindly for your attention to this. </p>]]></description>
          <pubDate>Sun, 25 Aug 2024 04:48:44 -0700</pubDate>
          <guid isPermaLink="true">forum-posts.php?postNum=2247456#post2247456</guid>
        </item>
                <item>
          <title>CMSB v3.71 Released (Jun 18) -Help Tooltips &amp; Upload Features</title>
          <link>https://interactivetools.com/forum/forum-posts.php?postNum=2247452#post2247452</link>
          <description><![CDATA[<p>Hi Craig, </p>
<p>We did fix this issue in the latest beta: <br />- Email Templates: Fixed issue where email templates would redirect back to edit page after saving</p>
<p>If that's the issue, it's saving but redirecting you back to the edit page.  </p>
<p>Let me know if that's it or what the error message is.  </p>
<p>Thanks!</p>]]></description>
          <pubDate>Thu, 22 Aug 2024 10:14:40 -0700</pubDate>
          <guid isPermaLink="true">forum-posts.php?postNum=2247452#post2247452</guid>
        </item>
                <item>
          <title>CMSB v3.71 Released (Jun 18) -Help Tooltips &amp; Upload Features</title>
          <link>https://interactivetools.com/forum/forum-posts.php?postNum=2247449#post2247449</link>
          <description><![CDATA[<p>Hi Dave</p>
<p>there is an issue with saving Email Templates they create a pop error about saving the template.</p>]]></description>
          <pubDate>Wed, 21 Aug 2024 16:55:41 -0700</pubDate>
          <guid isPermaLink="true">forum-posts.php?postNum=2247449#post2247449</guid>
        </item>
                <item>
          <title>CMSB v3.71 Released (Jun 18) -Help Tooltips &amp; Upload Features</title>
          <link>https://interactivetools.com/forum/forum-posts.php?postNum=2247378#post2247378</link>
          <description><![CDATA[<p>Hi Dave,</p>
<p>In my cases, it's a different value for each record.</p>
<p><strong>Example 1:</strong><br />A restaurant with 100 items updates their pricing with increases. Usually, at the same time, they will throw in some description changes of ingredients and such, or I'll be swapping some photos as well. So it's not just always 1 field—price, description, and photo.</p>
<p><strong>Example 2:</strong><br />A taphouse decides they want to list ABV percentages for all of their beers, and there are 100 in the database. Different values for each record but all the same ABV field.</p>
<p><strong>Example 3:</strong><br />I'm not going to lie—sometimes it may only be 7 weekly specials, but it's still efficient if possible! ;)</p>
<p>Thank you for considering this and thanks to the other interested users.</p>]]></description>
          <pubDate>Fri, 19 Jul 2024 12:16:03 -0700</pubDate>
          <guid isPermaLink="true">forum-posts.php?postNum=2247378#post2247378</guid>
        </item>
                <item>
          <title>CMSB v3.71 Released (Jun 18) -Help Tooltips &amp; Upload Features</title>
          <link>https://interactivetools.com/forum/forum-posts.php?postNum=2247377#post2247377</link>
          <description><![CDATA[<p>Hi Codee, </p>
<p>It's no problem at all and your comments are always welcome.  </p>
<p>We often explore many different ideas and then narrow them back down to the most essential features for the next step.  </p>
<p>That way we can develop/release something in a reasonable amount of time, while still being aware of where me might want to take in future.</p>]]></description>
          <pubDate>Fri, 19 Jul 2024 12:14:02 -0700</pubDate>
          <guid isPermaLink="true">forum-posts.php?postNum=2247377#post2247377</guid>
        </item>
                <item>
          <title>CMSB v3.71 Released (Jun 18) -Help Tooltips &amp; Upload Features</title>
          <link>https://interactivetools.com/forum/forum-posts.php?postNum=2247374#post2247374</link>
          <description><![CDATA[<p>I apologize for the intrusion and digression from the original post.</p>]]></description>
          <pubDate>Fri, 19 Jul 2024 11:48:53 -0700</pubDate>
          <guid isPermaLink="true">forum-posts.php?postNum=2247374#post2247374</guid>
        </item>
                <item>
          <title>CMSB v3.71 Released (Jun 18) -Help Tooltips &amp; Upload Features</title>
          <link>https://interactivetools.com/forum/forum-posts.php?postNum=2247373#post2247373</link>
          <description><![CDATA[<p>IF there are cons to this...maybe as a feature programmed into the top and bottom menus in the editor, or as an "advanced" option, or a checkbox in the General Settings section - to toggle the option?</p>]]></description>
          <pubDate>Fri, 19 Jul 2024 11:48:01 -0700</pubDate>
          <guid isPermaLink="true">forum-posts.php?postNum=2247373#post2247373</guid>
        </item>
                <item>
          <title>CMSB v3.71 Released (Jun 18) -Help Tooltips &amp; Upload Features</title>
          <link>https://interactivetools.com/forum/forum-posts.php?postNum=2247372#post2247372</link>
          <description><![CDATA[<p>Hi Rez, </p>
<p>Let's go back to the original use-case, what kinds fo things are you updating?  Is it that you need to update a single value across many records?  Or different values for each record?  </p>]]></description>
          <pubDate>Fri, 19 Jul 2024 11:19:21 -0700</pubDate>
          <guid isPermaLink="true">forum-posts.php?postNum=2247372#post2247372</guid>
        </item>
                <item>
          <title>CMSB v3.71 Released (Jun 18) -Help Tooltips &amp; Upload Features</title>
          <link>https://interactivetools.com/forum/forum-posts.php?postNum=2247350#post2247350</link>
          <description><![CDATA[<p>Initially I'm thinking when you click next record/prev record it should save the current one and then go to and open the chosen for editing.  As I mull it through my head, though, why not also incorporate an option that pops up when there is no more prev or next records (you've gone to one end or the other of the pile of records) that reads "There are no more (prev or next) records, do you wish to create a new one here?" </p>]]></description>
          <pubDate>Sat, 13 Jul 2024 14:18:01 -0700</pubDate>
          <guid isPermaLink="true">forum-posts.php?postNum=2247350#post2247350</guid>
        </item>
                <item>
          <title>CMSB v3.71 Released (Jun 18) -Help Tooltips &amp; Upload Features</title>
          <link>https://interactivetools.com/forum/forum-posts.php?postNum=2247347#post2247347</link>
          <description><![CDATA[<p>As in "auto-save" when pressing next? Good question. In Shopify, in a product's details, when you page "next" like this (or leave back to product list), it prompts you that you have unsaved changes and you have to press a save button before continuing with the next button again. I haven't made any mistakes nor have I been annoyed.</p>
<p>If pressing "next" saved and also went to the next record with that one click, it sounds convenient (I believe exiting without saving already causes a JS pop-up).</p>
<p>Can anyone think of any cons to this "save and next" button? I would think if you were pressing next, you are wanting to save every time. Otherwise, you cancel to revert?</p>
<p>Is that what you meant Dave? Sorry if I misunderstood. I'm fine with either way but more convenience is welcomed. I'm only experienced with Shopify which does work fine.</p>
<p>Thoughts anyone?</p>]]></description>
          <pubDate>Fri, 12 Jul 2024 20:29:47 -0700</pubDate>
          <guid isPermaLink="true">forum-posts.php?postNum=2247347#post2247347</guid>
        </item>
                <item>
          <title>CMSB v3.71 Released (Jun 18) -Help Tooltips &amp; Upload Features</title>
          <link>https://interactivetools.com/forum/forum-posts.php?postNum=2247345#post2247345</link>
          <description><![CDATA[<p>Hi All, </p>
<p>Thanks for the suggestion.</p>
<p>Would you want it to just "edit" the prev/next record or save the current record and then go to the prev/next record? </p>]]></description>
          <pubDate>Fri, 12 Jul 2024 16:26:27 -0700</pubDate>
          <guid isPermaLink="true">forum-posts.php?postNum=2247345#post2247345</guid>
        </item>
                <item>
          <title>CMSB v3.71 Released (Jun 18) -Help Tooltips &amp; Upload Features</title>
          <link>https://interactivetools.com/forum/forum-posts.php?postNum=2247336#post2247336</link>
          <description><![CDATA[<p>I'll second that!</p>
<p>~ Deborah</p>]]></description>
          <pubDate>Fri, 12 Jul 2024 04:21:33 -0700</pubDate>
          <guid isPermaLink="true">forum-posts.php?postNum=2247336#post2247336</guid>
        </item>
                <item>
          <title>CMSB v3.71 Released (Jun 18) -Help Tooltips &amp; Upload Features</title>
          <link>https://interactivetools.com/forum/forum-posts.php?postNum=2247334#post2247334</link>
          <description><![CDATA[<p>Hi Dave. Feature requests ok here? I think it would be nice if, while modifying a record, there were "next" and "previous" buttons to page through the list of records without having to back out to the full list view and come back in.</p>
<p>If this is possible, I believe it would be used a lot to update lists of records fast and efficiently.</p>
]]></description>
          <pubDate>Thu, 11 Jul 2024 23:46:28 -0700</pubDate>
          <guid isPermaLink="true">forum-posts.php?postNum=2247334#post2247334</guid>
        </item>
                <item>
          <title>CMSB v3.71 Released (Jun 18) -Help Tooltips &amp; Upload Features</title>
          <link>https://interactivetools.com/forum/forum-posts.php?postNum=2247291#post2247291</link>
          <description><![CDATA[<p>Hi Jeff, </p>
<p>Ok, glad to hear it's working now, and thanks for your feedback!</p>
<p>Cheers</p>]]></description>
          <pubDate>Fri, 21 Jun 2024 09:23:34 -0700</pubDate>
          <guid isPermaLink="true">forum-posts.php?postNum=2247291#post2247291</guid>
        </item>
                <item>
          <title>CMSB v3.71 Released (Jun 18) -Help Tooltips &amp; Upload Features</title>
          <link>https://interactivetools.com/forum/forum-posts.php?postNum=2247287#post2247287</link>
          <description><![CDATA[<p>Yes, a conflict existed. I use several symphony packages and PHP 8.3. Specifically, the symphony/polyfill, a dependency of other packages, was conflicting. My composer file calls your composer file using install and update hooks.. Without the composer.lock file, composer threw an error. </p>
<p>I had to generate a composer.lock file for CMSB using composer update, which updates your vendor files and resolves the conflict. If the lock file had been there, that would not have been necessary. My vendor directory is separate from yours as per best practices.</p>
<p>I am of the opinion, if you are going to use composer for what is essentially a subproject for everyone who does use composr, then you should follow recommended standards and best practices.</p>
<p>EDIT:</p>
<p>We can’t necessarily just drop a new version of CMSB on top of an older one. Plugin schemas, settings file, uploads and media files and directories need to be preserved. I use nodejs scripts to automate the process of updating CMSB.</p>
<p>I have 40 clients using one version of CMSB or another from 3.53 to 3.69. Whenever, they have a change, I take the opportunity to update CMSB and their version of PHP. </p>
<p>Recently I had to migrate my VPS fron Cloudlinux 7 with cpanel to cloundlinix 9 due to End of Life at the end of June. This also provided the opportunity to drop EOL PHP versions prior to 7.3.</p>
<p>I also use cypress.io to do complete e2e integration testing so all updates can be fully tested prior to pushing to the server. Every page is tested fo ensure no php errors, html-validated and ally for accessibility. I also use it to test Basic operation of CMSB when new versions come out.</p>]]></description>
          <pubDate>Thu, 20 Jun 2024 20:54:32 -0700</pubDate>
          <guid isPermaLink="true">forum-posts.php?postNum=2247287#post2247287</guid>
        </item>
                <item>
          <title>CMSB v3.71 Released (Jun 18) -Help Tooltips &amp; Upload Features</title>
          <link>https://interactivetools.com/forum/forum-posts.php?postNum=2247286#post2247286</link>
          <description><![CDATA[<p>Jeff, </p>
<p>Maybe let's back up here.  Beyond best practices, is there a specific problem you're trying to solve?  Is there something about the current setup that isn't working with your configuration?  e.g., conflicts between packages, etc?  </p>]]></description>
          <pubDate>Thu, 20 Jun 2024 20:00:05 -0700</pubDate>
          <guid isPermaLink="true">forum-posts.php?postNum=2247286#post2247286</guid>
        </item>
                <item>
          <title>CMSB v3.71 Released (Jun 18) -Help Tooltips &amp; Upload Features</title>
          <link>https://interactivetools.com/forum/forum-posts.php?postNum=2247285#post2247285</link>
          <description><![CDATA[<p>Hi Jeff, </p>
<p>The best practice of including a composer.lock file is for when you don't include a /vendor/ folder, as we are. Because we're including /vendor/ in our distribution, running composer install won't actually do anything at all, so it's redundant at this point.</p>
<p>There will be more Composer integration in future, but it's probably best to just ignore it for now. It's just how we're building the software behind the scenes.</p>
]]></description>
          <pubDate>Thu, 20 Jun 2024 19:54:49 -0700</pubDate>
          <guid isPermaLink="true">forum-posts.php?postNum=2247285#post2247285</guid>
        </item>
                <item>
          <title>CMSB v3.71 Released (Jun 18) -Help Tooltips &amp; Upload Features</title>
          <link>https://interactivetools.com/forum/forum-posts.php?postNum=2247284#post2247284</link>
          <description><![CDATA[<p>If others are not following best practices and modifying your composer file, they really need to rethink their approach. Forcing those who do follow best practices to NOT follow them is just wrong.</p>
<p>My 2 cents worth.</p>
<p>I believe you should follow best practices, and bring those who don’t do so, around instead of the other way around.</p>]]></description>
          <pubDate>Thu, 20 Jun 2024 19:12:41 -0700</pubDate>
          <guid isPermaLink="true">forum-posts.php?postNum=2247284#post2247284</guid>
        </item>
                <item>
          <title>CMSB v3.71 Released (Jun 18) -Help Tooltips &amp; Upload Features</title>
          <link>https://interactivetools.com/forum/forum-posts.php?postNum=2247283#post2247283</link>
          <description><![CDATA[<p>Hi Jeff, </p>
<p>You're completely right, but unfortunately, we need to support some additional use cases beyond what that document considers.  </p>
<p>Most users don't use composer at all and just upload the files, while others add custom packages and we don't want to overwrite their composer files on upgrade.  </p>
<p>What we could do for the next release is bundle the files as composer.json.default and composer.lock.default.  Then you could add a script section to your parent composer.json to rename those files if they're present, or maybe create symlinks from composer.json to composer.json.default.</p>
<p>Again, we're slowly migrating to Composer, and once you can install directly from Composer none of this is going to be an issue.  I'm cautious about spending too much time on a partial solution when it's all going to change anyway.  It's great if it works, but we're not officially supporting composer yet.  </p>
<p>All the same, I hope that helps and appreciate the feedback.  It lets us consider how to include support for your configuration in future builds.  Thanks!</p>]]></description>
          <pubDate>Thu, 20 Jun 2024 16:41:08 -0700</pubDate>
          <guid isPermaLink="true">forum-posts.php?postNum=2247283#post2247283</guid>
        </item>
                <item>
          <title>CMSB v3.71 Released (Jun 18) -Help Tooltips &amp; Upload Features</title>
          <link>https://interactivetools.com/forum/forum-posts.php?postNum=2247277#post2247277</link>
          <description><![CDATA[<p>Here is the recommened method for handling mutiple composer projects. CMSB is a sub project to my project with its own composer.json file. </p>
<p>When managing Composer dependencies for a project that is included in another Composer project, it's essential to ensure that dependencies are handled efficiently to avoid conflicts and ensure smooth integration. Here are some recommended methods to handle this scenario:</p>
<p>### 1. Use `composer.json` for Each Project</p>
<p>Each project should have its own `composer.json` file that lists its specific dependencies. This allows each project to declare its dependencies independently.</p>
<p>### 2. Rely on Composer's Dependency Resolution</p>
<p>Composer is designed to handle complex dependency trees. When you include a project as a dependency in another project, Composer will attempt to resolve all dependencies to their compatible versions. Ensure that the dependencies are correctly specified with version constraints in the `composer.json` files.</p>
<p>### 3. Use Semantic Versioning</p>
<p>Ensure that all projects follow semantic versioning (semver) for their dependencies. This helps Composer determine compatible versions and resolve conflicts. Semantic versioning uses a three-part version number: MAJOR.MINOR.PATCH.</p>
<p>- **MAJOR** version when you make incompatible API changes,<br />- **MINOR** version when you add functionality in a backward-compatible manner, and<br />- **PATCH** version when you make backward-compatible bug fixes.</p>
<p>### 4. Use `composer.lock` Files</p>
<p>Commit the `composer.lock` files to your version control system. The `composer.lock` file ensures that the exact versions of dependencies are installed, providing consistency across different environments.</p>
<p>### 5. Prefer Using `composer require`</p>
<p>When adding dependencies, use `composer require` instead of manually editing the `composer.json` file. This command automatically determines the appropriate version constraints based on the current versions available and any existing constraints.</p>
<p>### 6. Run `composer update` Carefully</p>
<p>Be cautious when running `composer update`. This command updates all dependencies to their latest versions within the specified constraints, which might introduce breaking changes. Instead, use `composer install` to install the dependencies as specified in the `composer.lock` file.</p>
<p>### 7. Use Version Constraints</p>
<p>Specify version constraints in your `composer.json` file to avoid unwanted updates. For example:<br />- `"package/name": "^1.2"` allows updates for all minor and patch versions within the 1.x range but not to 2.x.<br />- `"package/name": "~1.2.3"` allows updates for patch versions but not minor or major versions.</p>
<p>### 8. Utilize `conflict` and `provide` Sections</p>
<p>Use the `conflict` and `provide` sections in `composer.json` to explicitly declare incompatible versions or alternatives. This helps Composer resolve conflicts more effectively.</p>
<p>```json<br />{<br />"conflict": {<br />"vendor/package": "&gt;=2.0"<br />},<br />"provide": {<br />"vendor/alternative-package": "1.0.0"<br />}<br />}<br />```</p>
<p>### 9. Check for Compatibility</p>
<p>Periodically run `composer check-platform-reqs` to ensure that all dependencies are compatible with your PHP version and extensions.</p>
<p>### Example of Handling Dependencies</p>
<p>Consider a main project and a subproject, each with its own `composer.json`:</p>
<p>**Main Project (`main/composer.json`):**<br />```json<br />{<br />"require": {<br />"subproject/package": "^1.0",<br />"another/dependency": "^2.0"<br />}<br />}<br />```</p>
<p>**Subproject (`subproject/composer.json`):**<br />```json<br />{<br />"require": {<br />"subdependency/package": "^3.0"<br />}<br />}<br />```</p>
<p>When you run `composer install` in the main project, Composer will resolve the dependencies for both the main project and the subproject, ensuring compatibility and preventing conflicts.</p>
<p>By following these methods, you can efficiently manage Composer dependencies in complex projects and ensure a smooth integration process.</p>]]></description>
          <pubDate>Wed, 19 Jun 2024 16:07:48 -0700</pubDate>
          <guid isPermaLink="true">forum-posts.php?postNum=2247277#post2247277</guid>
        </item>
                <item>
          <title>CMSB v3.71 Released (Jun 18) -Help Tooltips &amp; Upload Features</title>
          <link>https://interactivetools.com/forum/forum-posts.php?postNum=2247276#post2247276</link>
          <description><![CDATA[<p>Hi Jeff, </p>
<p>We've actually been trying to work out how to best handle that for advanced users that use composer themselves for other purposes.  </p>
<p>The long term plan is to distribute CMSB via composer, but that's still a ways off.</p>
<p>The issue is that even bundling composer.json causes existing or updated composer.json files to get overwritten on upgrades.  For the next release we're planning to include it as composer.json.default and only rename/copy it to composer.json if there's no one there already so we don't overwrite existing updates.  The same would be true for the lock file, and I've already had to examine a couple lock files to determine what was installed previous to an upgrade to recreate it.</p>
<p>Can you run `composer update` to create/recreate the lock file? </p>]]></description>
          <pubDate>Wed, 19 Jun 2024 15:52:22 -0700</pubDate>
          <guid isPermaLink="true">forum-posts.php?postNum=2247276#post2247276</guid>
        </item>
                <item>
          <title>CMSB v3.71 Released (Jun 18) -Help Tooltips &amp; Upload Features</title>
          <link>https://interactivetools.com/forum/forum-posts.php?postNum=2247275#post2247275</link>
          <description><![CDATA[<p>Like the new features, however, I have a minor issue when updating a project. The composer.lock file is not included with the download. This causes an issue if you run composer install.</p>
<pre class="language-markup"><code>Installing dependencies from lock file (including require-dev)
Verifying lock file contents can be installed on current platform.
Warning: The lock file is not up to date with the latest changes in composer.json. You may be getting outdated dependencies. It is recommended that you run `composer update` or `composer update &lt;package name&gt;`.
- Required package "guzzlehttp/guzzle" is not present in the lock file.
- Required package "league/oauth2-client" is not present in the lock file.
- Required package "league/oauth2-google" is not present in the lock file.
- Required package "firebase/php-jwt" is not present in the lock file.
This usually happens when composer files are incorrectly merged or the composer.json file is manually edited.
Read more about correctly resolving merge conflicts <a href="https://getcomposer.org/doc/articles/resolving-merge-conflicts.md" rel="nofollow">https://getcomposer.org/doc/articles/resolving-merge-conflicts.md</a>
and prefer using the "require" command over editing the composer.json file directly <a href="https://getcomposer.org/doc/03-cli.md#require-r" rel="nofollow">https://getcomposer.org/doc/03-cli.md#require-r</a>
Script cd www/cmsb &amp;&amp; composer install &amp;&amp; echo 'successfully installed cmsb' handling the doCmsb event returned with error code 4
Script @doCmsb was called via post-install-cmd</code></pre>
<p>The composer.lock file should be included with the download.</p>]]></description>
          <pubDate>Wed, 19 Jun 2024 15:40:59 -0700</pubDate>
          <guid isPermaLink="true">forum-posts.php?postNum=2247275#post2247275</guid>
        </item>
                <item>
          <title>CMSB v3.71 Released (Jun 18) -Help Tooltips &amp; Upload Features</title>
          <link>https://interactivetools.com/forum/forum-posts.php?postNum=2247271#post2247271</link>
          <description><![CDATA[<p class="whitespace-pre-wrap break-words">Hi everyone,</p>
<p class="whitespace-pre-wrap break-words">We've just released another update.  Here is what's new: </p>
<ul class="list-disc pl-8 space-y-2 -mt-1">
<li class="whitespace-normal break-words"><strong>Help Tooltips:</strong> You can now add (?) help icon tooltips to field labels in the Field Editor.  These display beside the field label and show your help text on hover.  This is something we've started doing ourselves to simplify the interface while still allowing users to get additional info when they need it. It's handy for adding instructions or more details without cluttering up the interface.  </li>
<li class="whitespace-normal break-words"><strong>Upload Features:</strong> We added support for text boxes and required fields for upload info fields, so you can now require users to enter additional upload data, and/or give them a larger textbox to type it in.  As part of this upgrade we also automatically increased the field size of all the upload info* fields to support much more text if needed.</li>
</ul>
<p>Here's the complete changelog.</p>
<blockquote>
<pre>*** June 14, 2024 - Version 3.71 (Help Tooltips &amp; Upload Features)<br /><br />SERVER REQUIREMENTS: PHP 8.0+ and MySQL 5.7+ (or MariaDB 10.2+)<br /><br />NEW FEATURES<br />- Help Tooltips: You can now add (?) help icon tooltips to field labels in the Field Editor<br />- Upload Metadata: Added support for text boxes and required fields for upload info fields<br /><br />MINOR CHANGES &amp; BUG FIXES<br />- Backup: Added code to skip non-readable files and dirs<br />- Cookies: Regenerate cookie names to force the use of new cookie settings (will require re-login)<br />- Cookies: Limited max cookie age to one year for better compatibility with modern browsers and RFC 6265bis<br />- Cookies: Fixed issue that could cause multiple login cookies to be sent<br />- Checkbox CSS: Reverted checkbox styling to previous settings as per user feedback<br />- Backup: Backup size estimation now stops after 6 seconds for servers with many files<br />- ZenDB: Added $results-&gt;map() and $collection-&gt;implode() to simplify common HTML generation tasks<br />- Misc Code and other minor improvements.</pre>
</blockquote>
<p>You can download the latest version here: <a href="https://www.interactivetools.com/download/" rel="nofollow">https://www.interactivetools.com/download/</a></p>
<p>Please feel free to ask any questions or post any feedback, questions, concerns, or bugs you find! </p>
<p>Thanks, we look forward to your feedback! :)</p>]]></description>
          <pubDate>Tue, 18 Jun 2024 11:14:39 -0700</pubDate>
          <guid isPermaLink="true">forum-posts.php?postNum=2247271#post2247271</guid>
        </item>
              </channel>
    </rss>
  