primordic/IssueDupesLite huggingface dataset:
Repository: umbraco/Umbraco-CMS

Issue #13403: Date pickers select unexpected initial date
Created: 2022-11-15T09:52:41Z
Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)
10.3.0
Bug summary
When upgrading to Umbraco 10.3.0  (or higher) and adding a date picker to a document type the date picker is expected to select the current date. Instead it selects the 1st of last day of the month or even the 1st of january.
Specifics
No response
Steps to reproduce

Create an Umbraco project
Set a Date Picker (any) on DocType (LLL or MM-DD-YYYY)
Create a new page from DocType
Select a date for the first time
Select a new date and check if the calendar view starts at the 1st of the month.


Expected result / actual result

Expected to see the selection on the current date when opening calendar view
Actual result is 1st of last day of the month as initial selected date and sometimes even the 1st of january

Duplicate issue #15462: Date picker has incorrect date when editing and date format is NOT YYYY-MM-DD
Created: 2023-12-14T20:24:59Z
Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)
10..8.2
Bug summary
When datepicker is configured to display the date in a format such as DD/MM/YYYY or MM/DD/YYYY (i.e. not  YYYY-MM-DD) then when editing the date, the date shown in the calendar is not the date shown above.
Specifics

Steps to reproduce
Create a new Data Type using the Date Picker editor
Set the date format to DD/MM/YYYY
Create a Document Type that has a property with the Data Type that was created
Add Content with that Document Type
Set the value of the date to 15/12/2023
Save & publish content
Reload the page
Click the calendar icon
Expected result / actual result
Expected Outcome:

The calendar should show the date that was entered

Actual Outcome/Issue

The calendar shows 1 Jan of the year of the date.

Closing comment (2023-12-15T08:21:06Z): Sounds like this is a duplicate of #13403, can you confirm this? 🙈
Repository: umbraco/Umbraco-CMS

Issue #12757: Values saved as decimals on one culture display differently in another when using SQLite.
Created: 2022-08-01T09:25:02Z
Which exact Umbraco version are you using? For example: 9.0.1 - don't just write v9
10.1
Bug summary
When creating content with a decimal value using one culture and a Sqlite database, when switching cultures to one with a different decimal separator/group separator, the value displayed is not correct.
This issue was originally reported and is shown in this Umbraco Deploy issue, but likely the fix should be in CMS if it's possible as it can be replicated in other scenarios.
Specifics
I'm pretty sure the issue stems from using a TEXT data type for decimals rather than REAL.  This was changed in this PR, seemingly for good reason.  But coincidentally I had a database from prior to this change and I didn't see the problem in that.
I can see in SQLite Studio the value is stored as "123.0".
So this makes some sense, in that when loading this value under Danish culture, the "." would be considered as a numeric grouping separator leading to a value of "1230", which is what we see in the back-office when following the steps described below.
There's something confusing though.  If I create the content using the Danish culture, it's presented correctly under the Danish culture.  BUT if I look in the database, the value stored is still 123.0 (i.e. with a "." as the decimal separator).  So I don't understand why that displays OK.  Seemingly it's the same value that displays incorrectly if you switch cultures.
Steps to reproduce

Start using an en-US locale.  This can be done via regional settings or (more easily) by adding the following code to the Startup.Configure() method.

    var cultureInfo = new CultureInfo("en-US");

    CultureInfo.DefaultThreadCurrentCulture = cultureInfo;
    CultureInfo.DefaultThreadCurrentUICulture = cultureInfo;


Create a document type containing a property based on the decimal data type.
Create a content item and enter the value "123".
Amend the code above to use the Danish culture "da-DK"
Restart the application and note that the value is displayed as "1230"

Expected result / actual result
Should display the same across all cultures.

Duplicate issue #13135: Decimal field not saved in Russian localization
Created: 2022-10-06T12:20:25Z
Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)
10.2.1
Bug summary
In the Content section, an error pops up when trying to store a value in the Decimal field.
The error is observed in Russian localization.
Specifics
No response
Steps to reproduce

Select Russian localization.
Create a new page, add a decimal field
Add a value for this field to the Content and try to save

Expected result / actual result
No response

Closing comment (2023-01-27T10:00:08Z): I'll go ahead and close this one as it's a duplicate of #12757
Repository: umbraco/Umbraco-CMS

Issue #17313: Markdown doesn't render in block list item labels when using inline editing mode
Created: 2024-10-18T12:35:14Z
Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)
14.3.0
Bug summary
Umbraco Flavored Markdown does not render in block list item labels when using inline editing mode. The markdown does render correctly if inline editing mode is not enabled.
Specifics
No response
Steps to reproduce

Create a document type
Add a block list property editor
Select an element as an available block
Under Block appearance, in the Label field, add markdown to display a field value in the label (ex: {= title }
In content, create a document with the block list editor
Add an item to the block list providing a value for the field used in the label
Save it to see that the label is not rendered

Expected result / actual result
Expected result:
Markdown should render in the label. (the following screenshot is the block list with inline editing disabled)

Actual result
Markdown is not rendered in the label (the following screenshot is the block list with inline editing enabled)

Duplicate issue #17420: Vanilla UFM Block Label not rendering in Inline Editor Mode
Created: 2024-11-04T21:22:44Z
Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)
14.2.0
Bug summary
Using a block label such as {= menuItemText} on a block list containing elements that have an alias of "menuItemText" works great in most cases, but if I check the box in my block list data type to allow "Inline Editing" then the block labels do not render correctly, and instead just show the UFM syntax instead of the block instance property.
Specifics
Here is how my block renders normally

But if I toggle the 'Inline Editing' mode for this block list

My blocks render like this

Steps to reproduce
Create a block list with "Inline Editing" set to true.  Put a valid property name, in UFM syntax, in the block label for an allowed block
{= someValidProperty}
Now go in to the content tab and create an instance of your block list and you will not get the block labels you wanted to see.
Expected result / actual result
I can understand why this perhaps is tricky, but in some way the block labels need to reflect the current property value on the same screen as the property value that is being edited.  Is this in real-time as the user types on the keyboard? Or do they only reflect saved values?  I'm not sure I care but some support is probably better than no support for UFM

Closing comment (2024-11-04T22:04:14Z): Oops, duplicate of
#17313
Not interested in a package though
Repository: umbraco/Umbraco-CMS

Issue #11688: Naming a Block List property "navigation" breaks CSS
Created: 2021-11-23T16:24:03Z
Which exact Umbraco version are you using? For example: 9.0.1 - don't just write v9
9.1.1
Bug summary
If you add a property "navigation" to a contentype and add a blocklist to that. That alias will be set as the id-attribute on the "Add ..."-button, which in turn breaks the styling.

  
    
      Umbraco-CMS/src/Umbraco.Web.UI.Client/src/views/propertyeditors/blocklist/umb-block-list-property-editor.html
    
    
         Line 31
      in
      5bfab13
    
  
  
    

        
          
           id="{{vm.model.alias}}" 
        
    
  




Specifics
No response
Steps to reproduce

Create a doctype and add a property with the alias "navigation" to it.
Set the datatype to a block list.
Create a node with the doctype from step 1, the blocklist styling will look broken.

Expected result / actual result
I would prefix the ID with something. Personally, I'd also say "id" is the wrong attribute if you go by HTML conventions. ID is supposed to be guaranteed unique, this is not the case because an user could choose an alias that is also used by something else on the page. A "class" attribute would be better suited.

This item has been added to our backlog AB#25564

Duplicate issue #12995: Block list with alias "navigation" breaks button styling
Created: 2022-09-14T10:32:55Z
Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)
10.2.0
Bug summary
If a property of type Umbraco.BlockList has an alias of navigation, the button to add a new block has broken styling, obscuring block item properties.
Specifics
It looks to be because the property alias is used for the ID of the button element, so the styling for the content tree navigation (which also has an ID of navigation) overrides the button styling.


Steps to reproduce

Create any valid blocklist type.
Add a property of this blocklist type with the alias navigation to a document type.
Create content of this document type. The styling issue will be present for this property.

Expected result / actual result
Expected: The button to add a block should appear beneath any added blocks, inline with the clipboard button.
Actual: The button has full height across the property, obscuring block properties.

Closing comment (2022-09-14T10:41:04Z): Should've searched first - duplicate of #11688, sorry!
Repository: umbraco/Umbraco-CMS

Issue #12593: V10 - Changing UmbracoPath in appsettings does not work
Created: 2022-06-20T13:26:29Z
Which exact Umbraco version are you using? For example: 9.0.1 - don't just write v9
10.0.0
Bug summary
In v9 you are able to change the Umbraco backend url using the UmbracoPath appsetting. In v10 you will get a blank page when you change the backend url.
I think it has something to do with the new Umbraco.Cms.StaticAssets Razor library
Specifics
Chrome dev tools shows that the assets files are missing:

Steps to reproduce
Create a new umbraco site and install it as normal
modify appsettings.json
{
  "Umbraco": {
    "CMS": {
      "Global": {
        "ReservedPaths": "~/app_plugins/,~/install/,~/mini-profiler-resources/,~/my-secret-backend/,",
        "UmbracoPath": "~/my-secret-backend",
        "IconsPath": "~/my-secret-backend/assets/icons"
      },
    }
  }
}

run website again
goto https://localhost:44356/my-secret-backend
Expected result / actual result
Expect to see the Umbraco backend login page (like in v9)
Actual result was a blank page

This item has been added to our backlog AB#20467

Duplicate issue #12795: Custom backoffice URL in v10 not working after migration from v9
Created: 2022-08-06T12:04:20Z
Which exact Umbraco version are you using? For example: 9.0.1 - don't just write v9
10.0.1
Bug summary
Backoffice could not be run on custom url after upgrading from v9 to v10. It loads just blank white screen.
Specifics
No response
Steps to reproduce
Edit backoffice url on v10 installation. Follow this docs>
Rename your Umbraco-folder
https://our.umbraco.com/documentation/reference/security/Security-hardening/
Expected result / actual result
No response

Closing comment (2022-08-07T06:16:30Z): Duplicates #12593 - we'll work on it for a future release soon.
Repository: umijs/dumi

Issue #801: 在<code /> 引入的演示文件中  vscode提示当前找不到 如何处理 
Created: 2021-08-02T05:46:40Z

Duplicate issue #802: bug: 在 demo 中引入组件 提示找不到当前开发组件的ts类型
Created: 2021-08-02T06:08:10Z
Versions

dumi:
node:
npm:
OS:
Browser:

Steps to reproduce
What is Expected?
What is actually happening?

Closing comment (2021-08-02T06:22:35Z): Duplicate of #801
Repository: umijs/dumi

Issue #1530: bug: .dumirc中mfsu配置项中配置exclude后编译出错
Created: 2023-03-07T10:37:01Z
Versions

dumi: 2.1.15
node: 14.18.2
npm: 6.14.15
OS: Mac11.3.1
Browser: Chrome

Steps to reproduce
照着官网的文档创建一个新项目test-dumi
在组件库index.ts中随便写一个依赖，例如axios
import request from 'axios'

export function test() {
  console.log(request)
}

创建src/demos/Test.tsx组件，引用test函数
import React, { useEffect } from 'react'
import { test } from 'test-dumi'

export default function Test() {
  useEffect(() => {
    test()
  }, [])
  return (
    <div/>
  )
}

在脚手架初始化后的guide.md中添加demo
<code src="../src/demos/Test.tsx"></code>
在dumirc中更改mfsu的配置exclude掉axios
import { defineConfig } from 'dumi';

export default defineConfig({
  outputPath: 'docs-dist',
  themeConfig: {
    name: 'test-dumi',
  },
  mfsu: {
    exclude: ['axios']
  }
});

What is Expected?
启动项目可以正常编译
What is actually happening?
启动项目，编译报下面的错，去掉mfsu配置后编译成功

Duplicate issue #1538: bug: dumirc中配置mfsu.exclude后编译出错
Created: 2023-03-10T08:13:03Z
Versions

dumi: 2.1.15
node: 14.18.2
yarn: 1.9.4
OS: Mac11.3.1
Browser: Chrome

Steps to reproduce
test-dumi.zip
这里提供一个最小可复现代码，yarn install之后npm start即可复现编译失败
What is Expected?
期望可以正常编译
What is actually happening?

Closing comment (2023-03-10T08:14:38Z): Duplicate of #1530
Repository: umijs/dumi

Issue #580: feat: 【移动端主题】demo代码修改后，移动端主题展示不会热更新
Created: 2021-03-08T09:10:16Z
Description
dumi: 1.0.13
dumi-theme-mobile: 1.0.7
修改了demo代码，进行热更新，文档部分实时更新了，但是移动端模拟器上不会热更新，需要重启服务。
Solution

Duplicate issue #578: feat: 【移动端主题】demo代码修改后，移动端主题展示不会热更新
Created: 2021-03-08T09:08:25Z
Description
dumi: 1.0.13
dumi-theme-mobile: 1.0.7
修改了demo代码，进行热更新，文档部分实时更新了，但是移动端模拟器上不会热更新，需要重启服务。
Solution

Closing comment (2021-03-08T09:47:59Z): Duplicate of #580
Repository: umijs/dumi

Issue #777: Internationalization of code blocks
Created: 2021-07-17T15:50:57Z
Versions

dumi:  ^1.0.13
node: v15.6.0
npm: 7.4.0 (PS:  use Yarn 1.22.10,)
Browser: Chome 91.0.4472.124
OS:


Steps to reproduce

yarn create @umijs/dumi-lib
create example.zh-CN.md, example.md to folder
write content

example.md
<code src="../../../src/editor.tsx" title="Cell editing" desc="Provide a cell-editable table, Double click to edit" />

example.zh-CN.md
<code src="../../../src/editor.tsx" title="单元格编辑" desc="这是一个简单的自定义单元格编辑的表格, 双击可进行表格编辑" />


../../../src/editor.tsx is an arbitrary react component

What is Expected?
Not properly internationalized content

What is actually happening?
Should show different languages
I have a reproducible warehouse address here https://github.com/HighPerformanceComponent/rc-grid

git clone https://github.com/HighPerformanceComponent/rc-grid
yarn (PS: Yarn must be used)
yarn start:docs

\website\docs\getting-started\example\simple-example.md
\website\docs\getting-started\example\simple-example.zh-CN.md

Duplicate issue #840: Question:  切换英文时，组件代码块中的 title 、 desc 及代码中的文字，显示的是中文？
Created: 2021-08-19T10:28:22Z
Question
切换英文时，组件文档，代码块中的 title 和 desc 显示的是中文
Sample Code
复现仓库：https://github.com/niexq/react-auto-sizer
复现网址：https://niexq.github.io/react-auto-sizer
Versions

dumi: "^1.1.0"
node: "v12.18.4"
npm: 6.14.6
OS: macOS Big Sur
Browser: Google Chrome 版本 92.0.4515.131（正式版本） (x86_64)

Steps to reproduce
步骤：切换英文时，组件代码块中的 title 、 desc 及代码中的文字，显示的是中文

What is Expected?
切换英文显示英文
What is actually happening?
切换英文时，组件代码块中的 title 、 desc 及代码中的文字，显示的是中文

Closing comment (2021-08-19T15:41:35Z): 目前多语言配置要显式携带后缀，后续会支持自动识别
Duplicate of #777

好的，谢谢
Repository: umijs/dumi

Issue #1334: 可以在已有的umi下项目中集成dumi吗，官方文档中说明的不是很清楚
Created: 2022-11-29T07:21:13Z

Duplicate issue #2029: feat:umi4集成模式
Created: 2024-02-20T01:17:15Z
What problem does this feature solve?
umi4集成模式，现在有时间节点了吗？
Possible Solution (optional)
No response

Closing comment (2024-02-27T08:38:13Z): Duplicate of #1334
Repository: umijs/dumi

Issue #293: yarn build时报错'default' is not exported by node_modules/react-dom/index.js
Created: 2020-08-21T08:40:54Z
Question
yarn run v1.22.4
$ father-build
Clean dist directory
Build cjs with rollup
 ✖  error     Error: 'default' is not exported by node_modules/react-dom/index.js  at error (/Users/tsai/Desktop/rgulu-ui/node_modules/rollup/dist/rollup.js:5363:30) at Module.error (/Users/tsai/Desktop/rgulu-ui/node_modules/rollup/dist/rollup.js:9701:9) at handleMissingExport (/Users/tsai/Desktop/rgulu-ui/node_modules/rollup/dist/rollup.js:9618:21) at Module.traceVariable (/Users/tsai/Desktop/rgulu-ui/node_modules/rollup/dist/rollup.js:10009:17) at ModuleScope.findVariable (/Users/tsai/Desktop/rgulu-ui/node_modules/rollup/dist/rollup.js:8678:39) at FunctionScope.findVariable (/Users/tsai/Desktop/rgulu-ui/node_modules/rollup/dist/rollup.js:3054:38) at ChildScope.findVariable (/Users/tsai/Desktop/rgulu-ui/node_modules/rollup/dist/rollup.js:3054:38) at MemberExpression.bind (/Users/tsai/Desktop/rgulu-ui/node_modules/rollup/dist/rollup.js:6455:49) at CallExpression$1.bind (/Users/tsai/Desktop/rgulu-ui/node_modules/rollup/dist/rollup.js:3141:23) at CallExpression$1.bind (/Users/tsai/Desktop/rgulu-ui/node_modules/rollup/dist/rollup.js:6643:15) error Command failed with exit code 1.
之后我尝试把@types/classnames放在devDependencies 然后进行打包 也是报相同的错误
Sample Code
"dependencies": {
"@types/classnames": "^2.2.10",
"classnames": "^2.2.6",
"react": "^16.12.0"
},
"devDependencies": {
"@umijs/plugin-sass": "^1.1.1",
"@umijs/preset-react": "1.x",
"@umijs/test": "^3.0.5",
"dumi": "^1.0.9",
"father-build": "^1.17.2",
"gh-pages": "^3.0.0",
"lint-staged": "^10.0.7",
"prettier": "^1.19.1",
"yorkie": "^2.0.0"
}

Duplicate issue #1097: 'default' is not exported by moduleName
Created: 2022-05-30T08:30:57Z
Question
在组件文件中引入其他依赖，在构建时提示'default' is not exported by xxx，请问如何解决呢
Sample Code

Closing comment (2022-05-31T14:31:34Z): Duplicate of #293
Repository: umijs/dumi

Issue #1334: 可以在已有的umi下项目中集成dumi吗，官方文档中说明的不是很清楚
Created: 2022-11-29T07:21:13Z

Duplicate issue #2040: feat: dumi2集成umi4什么时候支持
Created: 2024-03-11T03:01:18Z
What problem does this feature solve?
我看咱们有计划做集成umi4，但是目前还是没有支持。
想问下，2024年还有计划吗？大概是怎样的。
Possible Solution (optional)
是否可以提供一个类似 @umijs/preset-dumi的插件

Closing comment (2024-03-24T07:14:47Z): Duplicate of #1334
Repository: umijs/dumi

Issue #748: 左侧菜单 最多只能生成二级吗？
Created: 2021-07-02T17:44:44Z
site 模式下
文件目录结构大概是这样的
/docs
    /一级
        /二级
            /三级
                /index.md

预期也是类似上图的左侧菜单
实际不是

Duplicate issue #1175:  请问site 模式，umirc.ts中自定义配置菜单支持三级路由嘛
Created: 2022-08-11T10:07:31Z

Closing comment (2022-08-11T16:24:20Z): Duplicate of #748
Repository: umijs/dumi

Issue #846: bug: Throw errors when i import something from 'dumi/theme'...
Created: 2021-08-24T09:04:31Z
Now i am tring to run code below:
import { usePrefersColor, context } from 'dumi/theme'; 
and i get this error:

But according to the documentation , what i am doing is allowed. How to avoid this kind of error?

In fact, there is a type hint when I move the mouse up:

Thanks!

Duplicate issue #848: bug: docs文件夹下，md引入脚本，脚本里面引入了dumi/theme，提示不能解析
Created: 2021-08-25T09:35:42Z
发现一个bug，操作如下：
首先在docs里面新建一个md文件，然后引入jsx，是可以正常显示页面的，因为我需要自定义页面，就像antd官网的组件总览一样
但是我需要获取到所有的路由，所以我这样写
import { context,} from 'dumi/theme';
const { menu } = useContext(context);
但是当我改变了md的文件夹之后，就提示我dumi/theme不能解析，具体错误提示如下：
Module build failed (from ./node_modules/@umijs/preset-dumi/lib/loader/index.js):
Error: Can't resolve 'dumi/theme' in 'D:/mlamp/projects/mlt-design/docs/components/src/overview'
后来我发现一个规律，在运行npm start启动之前如果没有引入dumi/theme的情况下，是完全可以正常启动的，然后再打开这几句代码，也是正常的，也可以获取到menu的，这都是正常的
问题在于：当我改变了该md之后，就会提示我以上错误，不能解析dumi/theme,我必须重复上面的操作才可以，也就是说，我在启动之后必须先把该模块的引用先注释了，才可以
当然，如果我不改变md内容的话，就是正常的，一旦改变就要重复上面的操作

Closing comment (2021-08-25T12:03:13Z): Duplicate of #846
Repository: unfoldadmin/django-unfold

Issue #384: Django authorisation accounts/password_change working, but accounts/password_reset not.
Created: 2024-05-13T18:48:39Z
I note that:
accounts/password_change has the expected unfold style:

But accounts/password_reset doesn't, looking into the html it seems that no tailwind styling is added like the reset view:

Just the basic reset password form is included, but it renders with limited usability:
<html>
<body>
<!--StartFragment-->
<form method="post"><input type="hidden" name="csrfmiddlewaretoken" value="SECRET">
--
  | <fieldset class="module aligned">
  | <div class="form-row field-email">
  |  
  | <label for="id_email">Email address:</label>
  | <input type="email" name="email" autocomplete="email" maxlength="254" required id="id_email">
  | </div>
  | <input type="submit" value="Reset my password">
  | </fieldset>
  | </form>

<!--EndFragment-->
</body>
</html>

On a white themed background (the default non-l;ogged in experience), this has almost no usability.

Duplicate issue #590: Forgot/reset password template missing
Created: 2024-07-17T09:04:06Z
I've enabled the forgot password option on login page, on logi the styling is ok

but when open the reset password link, the template styling is not working.

Am I missing something or the template is curently not yet developed in unfold admin templates?
Thanks, best regards

Closing comment (2024-07-18T09:58:02Z): Duplicate #384
Repository: unfoldadmin/django-unfold

Issue #366: Add support django-mptt
Created: 2024-05-04T13:11:24Z
Can you add support django mptt?

Duplicate issue #713: MPTTModelAdmin does not work with ModelAdmin
Created: 2024-09-02T14:54:21Z
MPTT admin does not compatible with django-unfold. Could you please help me to fix this?
code:
from mptt.admin import MPTTModelAdmin
from unfold.admin import ModelAdmin, TabularInline
@admin.register(ProductCategory)
class ProductCategoryAdmin(MPTTModelAdmin, ModelAdmin):
    list_display = ("title", "parent", "display_attributes", "display_tax_groups")
    search_fields = ("title",)
    mptt_level_indent = 20
    list_filter = ("parent",)
    inlines = [ProductCategoryAttributesInline, ProductCategoryTaxGroupsInline]

result:

Closing comment (2024-09-03T04:42:55Z): Hi, this is duplicate of #366 so I'm closing this ticket.
Repository: unfoldadmin/django-unfold

Issue #951: Can't add an item in [SectionInline] if WysiwygWidget is set in the form
Created: 2025-01-08T11:30:56Z
What version of Unfold are you using?
Problem is in 0.43 and 0.44
What version of Django are you using?
5.0.6
What browser are you using?
Version 131.0.6778.205 (Official Build) (64-bit)
Did you checked changelog/commit history, if the bug is not already fixed?
Yes
Did you searched other issues, if the bug is not already fixed?
Yes
Did you checked documentation?
Yes
Are you able to replicate the bug in the demo site?
No
Repository with reproduced bug
I'll do my best to get this setup for testing purposes.
Describe your issue
I'm getting this error when trying to add a new StackedInline item while having WysiwygWidget is set in the form: (this worked before updating to 0.43 and is still a problem in 0.44). If I remove the custom form from the class in admin, adding new items works fine. If I set extra to 1, that item gets created fine but I still can't use the "Add another" button without it throwing this error. I wonder if there is a conflict between the inlines.js and the wysiwyg editor?
Uncaught TypeError: Cannot set property name of # which has only a getter
at updateElementIndex (inlines.js:35:17)
at In. (inlines.js:99:9)
at Function.each (jquery.js:383:19)
at jQuery.fn.init.each (jquery.js:205:17)
at HTMLAnchorElement.addInlineClickHandler (inlines.js:98:21)
at HTMLAnchorElement.dispatch (jquery.js:5145:27)
at elemData.handle (jquery.js:4949:28)
admin.py:
class SectionInline(StackedInline):
model = Section
form = SectionForm
extra = 0
@admin.register(Page)
class PageAdmin(ModelAdmin):
list_display = ('title', 'last_updated', 'is_home', 'draft', 'template', 'slug')
inlines = [SectionInline]
forms.py:
from unfold.contrib.forms.widgets import WysiwygWidget
class SectionForm(forms.ModelForm):
class Meta:
model = Section
fields = "all"
widgets = {
'content': WysiwygWidget,
}

Duplicate issue #955: WysiwygWidget used with StackedInline Error
Created: 2025-01-10T12:39:50Z
What version of Unfold are you using?
0.44.0
What version of Django are you using?
4.2.16
What browser are you using?
Arc 1.74.0
Did you checked changelog/commit history, if the bug is not already fixed?
yes
Did you searched other issues, if the bug is not already fixed?
yes
Did you checked documentation?
yes
Are you able to replicate the bug in the demo site?
no
Repository with reproduced bug
Create minimal repository where it is possible to reproduce an error.
Describe your issue
I used WysiwygWidget for my inline model:
class TicketCommentInline(StackedInline):
model = TicketComment
formfield_overrides = {
models.TextField: {
"widget": WysiwygWidget,
}
}

it looks good, but when i clicked "add new" button, it had no effect, and i found an error in my browser console:

Closing comment (2025-01-14T08:09:49Z): Thanks for report but this is duplicate of #951
Repository: unfoldadmin/django-unfold

Issue #78: RTL implementation
Created: 2023-05-30T21:39:32Z
the Arabic admin panel version isn't working well at all since there isn't support for rtl

Duplicate issue #297: RTL‌ Support
Created: 2024-02-17T17:04:30Z
Possibility of RTL version
Are there styles?

Closing comment (2024-02-22T16:56:14Z): possibly its duplicate of #78
Repository: unfoldadmin/django-unfold

Issue #683: TabularInline: use one row per object (instead of two) to facilitate sorting
Created: 2024-08-15T18:59:03Z
Is it a third party application feature request?
No
Describe your feature request
Unfold's TabularInline template creates 2 rows per object (1 for the name, 1 for the fields) :

Django's TabularInline creates 1 row per object

This is not really a bug per se, but all 3rd party plugins offering a sortable functionality are expecting 1 row per object, and thus they are not compatible with Unfold. Wouldn't it be better to stick with native Django's structure ?
Possible solutions

Refactor Unfold TabularInline's template so that the object name is included in the same row as the fields
Implement a sortable feature in Unfold ?

Let me know what you think, I could draft a PR for either

Duplicate issue #699: "Run" Button Missing in Action List After Adding SortableAdminMixin
Created: 2024-08-24T07:49:25Z
What version of Unfold are you using?
0.34.0
What version of Django are you using?
4.2.6
What browser are you using?
Chrome 128.0.6613.84
Did you checked changelog/commit history, if the bug is not already fixed?
Yes
Did you searched other issues, if the bug is not already fixed?
Yes
Repository with reproduced bug
.
Describe your issue
I'm encountering an issue with Django admin when using the SortableAdminMixin. Specifically, after adding SortableAdminMixin to my Django admin configuration, the "Run" button for performing bulk actions, such as deleting multiple rows, is no longer visible.
Here's a brief overview of the problem:
Context: I am using SortableAdminMixin to enable sortable functionality in the Django admin interface. This mixin is designed to allow for drag-and-drop sorting of list items.
Problem: After incorporating SortableAdminMixin, the "Run" button, which is typically available for executing bulk actions (e.g., deleting selected rows), is no longer displayed in the action list dropdown menu.
Impact: This issue prevents users from performing batch actions on selected rows, which affects the usability and functionality of the admin interface for managing data efficiently.
Steps to Reproduce:
Add SortableAdminMixin to your admin class.
Observe the admin interface where the bulk action dropdown is displayed.
Notice that the "Run" button is missing from the action list.
Any guidance or solutions to resolve this issue would be greatly appreciated.

Closing comment (2024-09-13T13:37:57Z): I have the same issue.
In the list view, when I select some rows and want to run some action, there is no "Run" button there.
If I disable unfold in the settings, it appears again (as it usually exists in the original django admin).
And it's not a duplicate of #683
Repository: unfoldadmin/django-unfold

Issue #36: Input field not styled properly
Created: 2023-01-05T14:49:28Z
Above input field are not styled properly in detail.

It would be appreciated if list display for True/False field can add i18n support.
[x-cloak] { display: none !important; }
x-cloak style is also needed for hiding the user information dropdown menu until Alpine is fully loaded on the page.

Duplicate issue #72: Unstyled dropdown for actions in built in Django Sites
Created: 2023-05-23T22:07:58Z
Unfold Settings
UNFOLD = {
    "SITE_TITLE": "Bloop",
    "SITE_HEADER": "Double Bloop",
}


requirements.txt
asgiref==3.7.0
attrs==23.1.0
autobahn==23.1.2
automat==22.10.0
cffi==1.15.1
channels[daphne]==4.0.0
constantly==15.1.0
cryptography==40.0.2
daphne==4.0.0
django==4.2.1
django-extensions==3.2.1
django-phonenumber-field[phonenumberslite]==7.1.0
django-unfold @ git+https://github.com/unfoldadmin/django-unfold.git
djangorestframework==3.14.0
drf-extensions==0.7.1
drf-writable-nested==0.7.0
drfdocs2==0.0.16
hyperlink==21.0.0
idna==3.4
incremental==22.10.0
phonenumberslite==8.13.11
pyasn1==0.5.0
pyasn1-modules==0.3.0
pycparser==2.21
pygments==2.15.1
pyopenssl==23.1.1
pytz==2023.3
service-identity==21.1.0
shortuuid==1.0.11
six==1.16.0
sqlparse==0.4.4
twisted[tls]==22.10.0
txaio==23.1.1
typing-extensions==4.6.0
zope-interface==6.0

Closing comment (2023-05-24T16:30:47Z): Duplicate of #36
Repository: unfoldadmin/django-unfold

Issue #735: Missing "Add another" button when extra is zero, and no rows exist yet
Created: 2024-09-12T15:10:48Z
What version of Unfold are you using?
0.38.0
What version of Django are you using?
5.1.1
What browser are you using?
Chrome Version 128.0.6613.120 (Official Build) (arm64)
Did you checked changelog/commit history, if the bug is not already fixed?
Yes, not fixed with latest.
Did you searched other issues, if the bug is not already fixed?
Yes, not fixed with latest.
Describe your issue
When "extra" is zero and no rows exist yet in the stack inline, the "Add another [...]" button is missing. This issue occurs in the stack inline class only, not in the tabular. This issue was originally identified in PR #684.


Extra is "1" - button shows:



Extra is "0" - button is GONE:

Duplicate issue #753: Seems like StackedInline is broken if no records found
Created: 2024-09-18T14:26:00Z
What version of Unfold are you using?
Version: 0.38.0
What version of Django are you using?
For example: 5.1.1
What browser are you using?
For example: Doesn't matter
Did you checked changelog/commit history, if the bug is not already fixed?
Bug is in this commit
Are you able to replicate the bug in the demo site?

No add another record button, there is should be an additional condition if not inline_admin_formset.has_add_permission on line 16 in stacked.html (like in tabular.html)
So the final code on line 16 is: {% if not inline_admin_formset.has_add_permission and inline_admin_formset.forms|length == 0 %}

Closing comment (2024-09-20T10:21:13Z): Yes, you are right. This is duplicate of #735. I will take a look on that.
Repository: unfoldadmin/django-unfold

Issue #732: Version 0.38.0: Navigation Sidebar not working with Firefox anymore
Created: 2024-09-11T08:56:10Z
What version of Unfold are you using?
0.38.0
What version of Django are you using?
4.2
What browser are you using?
Firefox 115.14.0.ESR
Did you checked changelog/commit history, if the bug is not already fixed?
Yes
Did you searched other issues, if the bug is not already fixed?
Yes
Repository with reproduced bug
The Demo at https://demo.unfoldadmin.com/ also has the issue
Describe your issue
The Navigation Sidebar is not displayed:

Duplicate issue #755: Upgrading from django-unfold==0.35.0 to latest breaks the sidebar
Created: 2024-09-19T14:12:20Z
What version of Unfold are you using?
django-unfold==0.35.0
What version of Django are you using?
5.0
What browser are you using?
Chrome Version 128.0.6613.138 (Official Build)
Did you checked changelog/commit history, if the bug is not already fixed?
No
Did you searched other issues, if the bug is not already fixed?
Yes
Did you checked documentation?
Yes, couldn't find any references.
Are you able to replicate the bug in the demo site?
Haven't tried
Repository with reproduced bug
Create minimal repository where it is possible to reproduce an error.
Describe your issue
The sidebar menu doesn't show when I upgrade to the latest version.

Closing comment (2024-09-20T00:15:32Z): Clear your browser cache and try again.
This is related to #732 .
Repository: unfoldadmin/django-unfold

Issue #384: Django authorisation accounts/password_change working, but accounts/password_reset not.
Created: 2024-05-13T18:48:39Z
I note that:
accounts/password_change has the expected unfold style:

But accounts/password_reset doesn't, looking into the html it seems that no tailwind styling is added like the reset view:

Just the basic reset password form is included, but it renders with limited usability:
<html>
<body>
<!--StartFragment-->
<form method="post"><input type="hidden" name="csrfmiddlewaretoken" value="SECRET">
--
  | <fieldset class="module aligned">
  | <div class="form-row field-email">
  |  
  | <label for="id_email">Email address:</label>
  | <input type="email" name="email" autocomplete="email" maxlength="254" required id="id_email">
  | </div>
  | <input type="submit" value="Reset my password">
  | </fieldset>
  | </form>

<!--EndFragment-->
</body>
</html>

On a white themed background (the default non-l;ogged in experience), this has almost no usability.

Duplicate issue #905: User management questions
Created: 2024-12-17T17:52:13Z
I am using the latest unfold version but I have a couple of question that I wasn't able to resolve reading the doc and the source code.

How I can enable the recovery password for this admin dashboard for the users? Ref #590
How I can customize the user creation form to add the email field as example?

Closing comment (2024-12-17T18:02:24Z): I think you already answered your first question in the original issue. It requires manual implementation which is out the scope of Unfold. In the same issue, I'm pointing it is a duplicate of #384 where I'm providing detailed explanation.
For changing the form in Django admin you can configure add_form property in ModelAdmin to point at the custom form.
Repository: unisonweb/unison

Issue #802: commands to list immediate dependents / dependencies for a definition
Created: 2019-09-17T18:56:08Z

Duplicate issue #927: Example usage/tests in ucm
Created: 2019-11-03T20:58:35Z
I'm not sure what the difference is between usage/examples/tests, but maybe "examples" and "tests" are the same, and "usage" just refers to a canonical example? Maybe there's a way to set a particular test as canonical?
usage
view.usage .base.Int.maxInt
          > .base.Int.maxInt
          ⧩
          +9223372036854775807

tests
view.tests .base.Int.mod
    > .base.Int.mod +12 +3
    ⧩
    +0

    > .base.Int.mod +12 +4
    ⧩
    +0

    > .base.Int.mod +12 +5
    ⧩
    +2

Closing comment (2019-11-04T17:06:23Z): Would we say this is a duplicate of #802 ?
Repository: unisonweb/unison

Issue #1502: Crash when pulling
Created: 2020-05-01T14:14:36Z
On ucm version release/M1l:
.> pull https://github.com/zenhack/unison-parsers.git parsers
ucm: 😞 I was trying to copy a term fromcodebase...                        
        /Users/thoradam/.unison/v1/terms/#lj5rkikgh4co2alhitrghobej29gb5gojagk3vistb5uihpfksv9jo4g3gmgeh2ilm6q4tvkfqi8mcv7ntp680jp57denlpmddu062o/compiled.ub
but there was nothing there.
CallStack (from HasCallStack):
  error, called at src/Unison/Codebase/FileCodebase/Reserialize.hs:125:16 in unison-parser-typechecker-0.1-1n4fxMa6V58C0oQoOr6uen:Unison.Codebase.FileCodebase.Reserialize

@aryairani looked into it:

There was a bug in ucm at the time that that repo (zenhack/unison-parsers) was created, which caused it to be created incompletely.

Duplicate issue #1505: when trying to pull: "unison: user error trying to copy the definition of #cf8c1"
Created: 2020-05-01T22:35:09Z
[the raw version of this issue description is a valid unison transcript demonstrating the problem]
Net effect is some unison code I pushed a while ago can't be retrieved.  There have probably been a bunch of fixes to the push/pull mechanism since then I guess.  I still have the code in one of my local codebases so no biggie.
.> pull https://github.com/unisonweb/base:.trunk .base
.> pull https://github.com/atacratic/unison-datetime.git _unison_datetime

crashes ucm with the following message during the second pull...
unison: user error (😞 I was trying to copy the definition of #cf8c1, but I couldn't find it as a type _or_ a term.)

when I restart and check that hash I see...
.> names #cf8c1

  Term
  Hash:   #cf8c1a0tu8
  Names:  _base.releases._M1j.test.internals.v1.Test.run
          _base.releases._M1j.test.run
          _base.releases._M1k.test.internals.v1.Test.run
          _base.releases._M1k.test.run
          _base.releases._M1l.test.internals.v1.Test.run
          _base.releases._M1l.test.run
          _base.releases._latest.test.internals.v1.Test.run
          _base.releases._latest.test.run
          _base.trunk.test.internals.v1.Test.run
          _base.trunk.test.run
          base.test.internals.v1.Test.run
          base.test.run


Is https://github.com/atacratic/unison-datetime.git broken?

Closing comment (2020-05-01T23:38:47Z): Possible duplicate of #1502, although it's interesting that the error message isn't the same.
Repository: unisonweb/unison

Issue #4084: Spurious ability check failure here
Created: 2023-06-09T18:13:23Z
foo : forall g . ('{g} () ->{g} ()) -> Nat
foo g = todo g

wat : ('{IO} () ->{IO} ()) ->{} Nat
wat f = foo f
  The expression in red

                needs the abilities: {IO}
    but was assumed to only require: {}

  This is likely a result of using an un-annotated function as an argument with concrete abilities. Try adding an annotation to the function definition whose body is red.

     10 | wat f = foo f
                      ^-- error here

There seems to be no workaround (I tried putting annotations on f at the call site to no avail)

Duplicate issue #4135: Can't construct type that "holds" a function that references an ability by variable on both the input and output
Created: 2023-06-26T18:10:08Z
Using development version: 39b76f3
unique type Holder g
  = Holder ('{g} () ->{g} ())

main = do
  fn : '{IO} () ->{IO} ()
  fn effect = !effect

  v : Holder IO
  v = Holder fn
  ()

  The expression in red
  
                needs the abilities: {IO}
    but was assumed to only require: {}
  
  This is likely a result of using an un-annotated function as an argument with concrete abilities. Try adding an annotation to the function definition whose body is red.
  
     10 |   v = Holder fn

This is possibly a simpler version of the following issue:
#4134

Closing comment (2023-06-26T18:29:25Z): I think this is a duplicate of #4084
Repository: unisonweb/unison

Issue #2801: ucm command: view only type signature
Created: 2022-01-13T04:28:05Z
I find that I'm often just interested in the type signature of a term, but  when I view myTerm the implementation is long enough that I have to page back to see the type signature. It'd be nice to have an easy way to view just the type signature.
For example instead of:
.> view .base.List.map

  base.List.map : (a ->{𝕖} b) -> [a] ->{𝕖} [b]
  base.List.map f a =
    go i as acc =
      match List.at i as with
        None   -> acc
        Some a ->
          use Nat +
          go (i + 1) as (acc :+ f a)
    go 0 a []

I'd want something like:
.> signature .base.List.map

  base.List.map : (a ->{𝕖} b) -> [a] ->{𝕖} [b]

Some possible command names that come to mind:

signature List.map
view.signature List.map
view : List.map (similar to using find : to find by type, but I think that this is unnecessarily cryptic and don't really like it)
type List.map
typeOf List.map
view.type List.map

NOTE: if the fzf completion options showed the type signature when doing the no-arg version of view that would probably be good enough for me and I don't know that I'd feel the need for a separate command.

Duplicate issue #5445: `typeof` command to just print the type of a term in ucm without printing the body and cluttering the terminal
Created: 2024-11-06T16:05:46Z

Closing comment (2024-11-06T17:10:51Z): I think this is a duplicate of #2801
Repository: unisonweb/unison

Issue #525: Prettyprinter should do something to avoid conflicts between local names and names chosen for any refs
Created: 2019-06-20T19:47:36Z
Paul will do a longer writeup of this issue.

Duplicate issue #4207: Pretty-printer produces conflict when function is shadowed by binding
Created: 2023-07-18T14:43:21Z
Version: release/M5b
Original code:
ticksPerQuarterNote = settings |> SequencerSettings.ticksPerQuarterNote

Pretty-printed code (produces type error):
ticksPerQuarterNote = settings |> ticksPerQuarterNote

It doesn't round trip since now the function name conflicts with the binding name.

Closing comment (2023-07-18T14:53:46Z): This one is a dupe of #525 which is ancient. I'll take a look at it, I don't think there's any real holdup.
Repository: unisonweb/unison

Issue #4729: Roundtrip bug in syntax.docCallout.doc
Created: 2024-02-28T16:49:05Z
This parses fine:
foo =
  docCallout
    (Some
      {{
      # Title
      
        
      }}) {{ This is a callout with a title }}

But this doesn't:
syntax.docCallout.doc : Doc
syntax.docCallout.doc =
  {{
  A callout is a block of text that is visually distinct from the surrounding
  text. It is used to draw attention to important information.
  
  # Examples
  
    ```
    docCallout None {{ This is a callout }}
    ```
    
    ```
    docCallout (Some {{ 👋 }}) {{ This is a callout with an emoji }}
    ```
    
    ```
    docCallout
      (Some
        {{
          # Title
        
          
        }}) {{ This is a callout with a title }}
    ```
  }}

Seems to fail to parse doc syntax inside the example block in a doc

Duplicate issue #4476: DocTable no longer supports Header elements in cells
Created: 2023-12-05T23:43:15Z
I've been trying to get some website updates done and fighting what appear to be a few Docs regressions.
This minified Doc shows the problem where header elements # used to be able to be table headings, but are now rejected.
whatProblemsDoesUnisonSolve : Doc
whatProblemsDoesUnisonSolve = {{

  # What problems does Unison solve?

    {{ docTable [ [{{ # The problem }}, {{ # Our remedy }}]
      , [ {{
          a
          }}
        , {{
          b
          }}
        ]
      ] }}
  }}

The error is
  offset=128:
  unexpected "# "
  expecting "}}" or white space

Closing comment (2024-06-13T19:59:05Z): Heya, might be wrong but I'm wondering if this is actually related (if not the same) as #4729 🤔  I've been looking into that one and this seems almost identical, especially since if we add an extra # to the inner headings then it seems to parse?
    whatProblemsDoesUnisonSolve : Doc
    whatProblemsDoesUnisonSolve = {{
    
      # What problems does Unison solve?
    
        {{ docTable [ [{{ ## The problem }}, {{ ## Our remedy }}]
          , [ {{
              a
              }}
            , {{
              b
              }}
            ]
          ] }}
      }}

witty-toad/main> add

  ⍟ I've added these definitions:

    whatProblemsDoesUnisonSolve : Doc

witty-toad/main> display whatProblemsDoesUnisonSolve

  # What problems does Unison solve?

    # The problem   # Our remedy
    a               b

witty-toad/main>
Repository: unisonweb/unison

Issue #3502: new system for choosing compatible `base` versions for new setups
Created: 2022-10-13T16:54:26Z
Ideally we could release base and ucm independently, while ensuring that ucm won't hand a developer a version of base that requires unknown builtins.
Ideally, minimal manual work incurred when adding builtins or releasing ucm or releasing base.

Duplicate issue #3501: Empty codebase should pull highest matching release of base
Created: 2022-10-13T16:54:17Z

Closing comment (2022-10-13T16:58:52Z): close as dupe of #3502
Repository: unisonweb/unison

Issue #448: Make TDNR more predictable
Created: 2019-04-09T00:33:33Z
I'd like TDNR to be more predictable. Lately I've been avoiding it since it gives odd results unless the rest of the code also typechecks (often not the case).
Something that might be relevant is that the way we currently select possibilities is by putting a blank in the program and then running typechecking to learn the type of that blank. If the program has type errors elsewhere, it's possible that inserting that blank may cause the program to typecheck, but with a weird type for the blank.
I'd probably start by collecting a number of examples of behavior we don't like for TDNR, then see if we can come up with something that's highly predictable.
Or it might be that TDNR is fine and just needs better docs and a few bugfixes.
Related issues:
#377 #376 #370 #366 #845

Duplicate issue #366: Complains about known unknown type
Created: 2019-03-08T13:51:37Z
type Value = Nested Value
           | Foo

Foo.format : Value -> Text
Foo.format v = case v of
  Value.Foo     -> "foo"
  Value.Nested v -> Foo.format v

> format (Value.Nested Value.Foo)
As you can see below this fails to compile and the error points to the correct Foo.format but says it doesn't know about it?
master>
I don't know about the type Foo.format.  Make sure it's imported and spelled correctly:

    9 | > format (Value.Nested Value.Foo)

If we switch to the fully qualified name the watch expression executes correctly
  ┌
  │  9 | > Foo.format (Value.Nested Value.Foo)
  │        ⧩
  │        "foo"
  └

And strangely another way to fix this is to not use the fully qualified name in the case
type Value = Nested Value
           | Foo

Foo.format : Value -> Text
Foo.format v = case v of
  Value.Foo     -> "foo"
  Value.Nested v -> format v

> format (Value.Nested Value.Foo)
  ┌
  │  9 | > format (Value.Nested Value.Foo)
  │        ⧩
  │        "foo"
  └

Closing comment (2019-04-29T18:34:12Z): This example works fine in current master, so I'm going to close, but we're probably going to revisit how TDNR works, tracked in #448.
Repository: unocss/unocss

Issue #3293: Confusion over the order of the same rules
Created: 2023-10-31T08:18:39Z
UnoCSS version
0.57.1
Describe the bug
As with the minimal implementation, it's not retrieved from the beginning nor the end, instead it uses red in the middle, but that's not to say that it's necessarily the middle, my feeling seems to be that there's a set of default rules in order for a reason, but that doesn't cover the same rules
Reproduction
https://stackblitz.com/edit/nuxt-starter-a4phwp?file=app.vue
System Info
System:
OS: Linux 5.0 undefined
CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
Memory: 0 Bytes / 0 Bytes
Shell: 1.0 - /bin/jsh
Validations

 Read the Contributing Guidelines.
 Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
 Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
 The provided reproduction is a minimal reproducible example of the bug.

Duplicate issue #3338: unocss className priority is inexact
Created: 2023-11-15T09:34:04Z
UnoCSS version
0.57.3
Describe the bug
I have a component Foo, Its initial height is 200px
export const Foo = ({className=''}:{className?:string}) => {
  return (
    <div className={`b-solid h-200px ${className}`}>Foo</div>
  )
}
When I used it externally and re-set the height to 100px, I expected 100px but unfortunately I got 200px
import { Foo } from './Foo'

function App() {
  return (
    <div>
      <Foo className='h-100px' />
    </div>
  )
}

export default App

One solution is to add for subsequent styles !important, but this is so weird
import { Foo } from './Foo'

function App() {
  return (
    <div>
      <Foo className='!h-100px' />
    </div>
  )
}

export default App
Reproduction
export const Foo = ({className=''}:{className?:string}) => {
  return (
    <div className={`b-solid h-200px ${className}`}>Foo</div>
  )
}

function App() {
  return (
    <div>
      <Foo className='h-100px' />
    </div>
  )
}
System Info
No response
Validations

 Read the Contributing Guidelines.
 Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
 Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
 The provided reproduction is a minimal reproducible example of the bug.

Closing comment (2023-11-15T09:53:44Z): duplicate: #3293