jkersu

Anyone know a smart way to tell where a User is coming from (country) i.e. based on IP address or some other geotargeting method? We have 2 versions of a page where we want a certain version to be shown depending on the country of the user

jkersu

Anyone have tips speeding up a Docker container on Windows? It takes quite a bit of time to run dev build for larger projects. Is it recommended to mount the project workspace in a volume first or just directly inside the container?

Also has anyone use docker-sync on windows before? Any good?

jkersu

Yes you should be able to, as your CustomElementalBlock extends off BaseElement which extends off DataObject 🙂

jkersu

You can either build the dropdown manually without scaffolding (more complicated) or just update the limit on the Field Type in your own config, depending on how many items you have in your dropdown 🙂

jkersu

Set to 100 by default: https://github.com/silverstripe/silverstripe-framework/blob/4/src/ORM/FieldType/DBForeignKey.php#L40

More information: https://github.com/silverstripe/silverstripe-framework/pull/7789

Show 5 attachment(s)
src/ORM/FieldType/DBForeignKey.php:40

[silverstripe/silverstripe-framework] src/ORM/FieldType/DBForeignKey.php:40

src/ORM/FieldType/DBForeignKey.php:40

[silverstripe/silverstripe-framework] src/ORM/FieldType/DBForeignKey.php:40

#7789 make dropdownFieldThreshold configurable on DBForeignKey

[silverstripe/silverstripe-framework] #7789 make dropdownFieldThreshold configurable on DBForeignKey

src/ORM/FieldType/DBForeignKey.php:40

[silverstripe/silverstripe-framework] src/ORM/FieldType/DBForeignKey.php:40

#7789 make dropdownFieldThreshold configurable on DBForeignKey

[silverstripe/silverstripe-framework] #7789 make dropdownFieldThreshold configurable on DBForeignKey

Hide attachment content
jkersu

My bet is on DataObject::getSchema() maybe? 😂

jkersu

Right... this may be related (note its for versioned objects in the many-many relation so not sure if the same applies for non-versioned objects): https://github.com/silverstripe/silverstripe-versioned/issues/200

Show 1 attachment(s)
UndefinedOffset

Affected Version

silverstripe/recipe-cms 4.3.0
silverstripe/versioned 1.3.0

Description

In SilverStripe 4.3.0 (at least) when you have a many_many through relationship that is versioned (on both the junction and the end objects) the "Archive" button provided through GridFieldArchiveAction does not archive the junction object it archives the end object. As well the junction object's row remains in the database.

As a side (not sure if it's my install or not it's possible found on a very big site) the alert to confirm the action is empty in Firefox 64 at least.

Expected

The junction object would be removed but the end object of the relationship would not be.

Steps to Reproduce

  1. Have a many_many through relationship that has the junction and end objects versioned
  2. Add one of the end objects to the relationship
  3. Click the archive button
  4. Check the end object and it is now archived

Pull requests

https://github.com/silverstripe/silverstripe-versioned/pull/246|#246

Hide attachment content