We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
多图片时,数据库中存储图片的名称如(逗号分隔的多个图片,此格式jeecgboot online表单中自动存储成这样的格式):DiversityAvatarBoy012x_1695531509570.png,DiversityAvatarBoy022x_1695531515572.png,DiversityAvatarBoy032x_1695531519894.png,DiversityAvatarBoy042x_1695531523620.png,DiversityAvatarBoy052x_1695531528526.png,DiversityAvatarBoy062x_1695531533326.png,DiversityAvatarBoy072x_1695531537122.png,DiversityAvatarBoy082x_1695531544184.png 此情况下,导出excel时,这个字段的图片一个也导不出,问题可能出现在下面这个类的相关代码 autopoi版本:1.4.6 类及方法:org.jeecgframework.poi.excel.export.base.ExcelExportBase.createImageCell 相关代码: if(!entity.getImageBasePath().endsWith(File.separator) && !imagePath.startsWith(File.separator)){ path = entity.getImageBasePath()+File.separator+imagePath; }else{ path = entity.getImageBasePath()+imagePath; }
The text was updated successfully, but these errors were encountered:
No branches or pull requests
多图片时,数据库中存储图片的名称如(逗号分隔的多个图片,此格式jeecgboot online表单中自动存储成这样的格式):DiversityAvatarBoy012x_1695531509570.png,DiversityAvatarBoy022x_1695531515572.png,DiversityAvatarBoy032x_1695531519894.png,DiversityAvatarBoy042x_1695531523620.png,DiversityAvatarBoy052x_1695531528526.png,DiversityAvatarBoy062x_1695531533326.png,DiversityAvatarBoy072x_1695531537122.png,DiversityAvatarBoy082x_1695531544184.png
此情况下,导出excel时,这个字段的图片一个也导不出,问题可能出现在下面这个类的相关代码
autopoi版本:1.4.6
类及方法:org.jeecgframework.poi.excel.export.base.ExcelExportBase.createImageCell
相关代码:
if(!entity.getImageBasePath().endsWith(File.separator) && !imagePath.startsWith(File.separator)){
path = entity.getImageBasePath()+File.separator+imagePath;
}else{
path = entity.getImageBasePath()+imagePath;
}
The text was updated successfully, but these errors were encountered: