Blog

Luis Majano

June 12, 2019

Spread the word


Share your thoughts

Modernize all things!

FORGEBOX v4.7.0 released!

Today we are pleased to announce a minor release for our FORGEBOX suite of products to version 4.7.0. This release includes lots of fixes and some great additions.

Release Notes

Here are the detailed release notes for this release.

Bugs

  • [FORGEBOX-163] - box.json validation error while adding version from web UI completely clears screen and loses data
  • [FORGEBOX-298] - Adding version allows the user to check the "stable" checkbox
  • [FORGEBOX-355] - Update s3sdk settings configuration to include building the URL to avoid empty issues
  • [FORGEBOX-358] - Forgebox Registration page "Privacy Policy" link is broken/ not set. Clicking on it loses the page and all the form values you've filled out.
  • [FORGEBOX-359] - Mailing list checkbox on registration page is not working when selected
  • [FORGEBOX-360] - Blanks is displayed when Editing a package on packages with html markup
  • [FORGEBOX-361] - Fix Ownership of packages issue when publishing from collaborators
  • [FORGEBOX-362] - Button for adding a new version not firing
  • [FORGEBOX-365] - Admin cannot change username, fails with exception
  • [FORGEBOX-371] - Error creating versions, fails with exceptions from UI
  • [FORGEBOX-372] - Error calling admin:settings.getLiveActivations from UI
  • [FORGEBOX-374] - Do not show badges if package does not have any version
  • [FORGEBOX-375] - Do not show version badge if the package does not have any version

New Features

  • [FORGEBOX-322] - Fine tuning of public versions tab with much better UX
  • [FORGEBOX-324] - Reset Password action from user listing screen for admins
  • [FORGEBOX-332] - Create the beginnings of the Package Dependency Viewer in the UI
  • [FORGEBOX-334] - Add latest version badge to the package view top section
  • [FORGEBOX-335] - Add package type badge (public,private) on the package view section

Improvements

  • [FORGEBOX-138] - Show code to make ForgeBox badges on the package maintainer screen.
  • [FORGEBOX-351] - Change user dashboard links on the public UI to @username for consistency and just plain nice!
  • [FORGEBOX-366] - Upgrade to ColdBox 5.4.1
  • [FORGEBOX-367] - Upgrade of mementifier to latest version
  • [FORGEBOX-368] - Upgrade to sentry for logging
  • [FORGEBOX-369] - Upgrade s3sdk to avoid debugging code
  • [FORGEBOX-370] - Upgrade to testbox 3

Add Your Comment

Recent Entries

Why BoxLang When You Have Kotlin, Groovy, Scala, and more…

Why BoxLang When You Have Kotlin, Groovy, Scala, and more…

As we approach a stable release of BoxLang and our continued marketing reaches more folks, many have asked about its purpose. Why create a new language when the JVM ecosystem already includes established languages like Kotlin, Groovy, and Scala, to name a few.

Luis Majano
Luis Majano
December 18, 2024
ColdBox Free Tip 6 - Using Routing with Wildcard Domains!

ColdBox Free Tip 6 - Using Routing with Wildcard Domains!

ColdBox gives you the flexibility to create domain-specific routes, making it perfect for multi-tenant applications or projects that need to respond differently based on the domain or subdomain being accessed. In this tip, we’ll dive into how to use the withDomain() method to create routes that match specific domains or sub-domains.

Maria Jose Herrera
Maria Jose Herrera
December 18, 2024