I had created a custom Content type: "UpComingProducts" in Orchard. This content type had an Image Picker field.
While exporting this Custom Content type: "UpComingProducts", i do select the Images as well in addition to the Metadata and the Data for "UpComingProducts" .
Problem is that on importing, the Content Data is imported successfully but the Images are not getting imported. I checked the "Media" link in Admin Menu and also the Media folder on filesystem, there are NO images there after import.
Please help me here. Why Images are not imported but the rest of custom content is importing properly ?
Related
I am facing issue in a document library having a folder with a Document Set content type.
When I am uploading a document into a folder, it's uploaded successfully. but unfortunately, it's not appearing in that specific folder.
i.e.
The Document Library's name is Docs:
Docs Library Has many folders like Test, Test2, A, B, C,..Z.
I have uploaded the document into the A folder. upload successfully. but when investigating that folder (A Folder) it shows blank.
Document Library Url:
https://SharepointSite/sites/demo/docs
Folder Url :
https://SharepointSite/sites/demo/Docs/Forms/Document Set/docsethomepage.aspx?ID=14&FolderCTID=0x0120D52000753AFBDDB7855346B49428FBECC2D036&List=1b378e5e-6da5-4a18-bfe3-2de3dd57849b&RootFolder=/sites/demo/Docs/A&RecSrc=/sites/demo/Docs/A
One more thing.
When I search document name in the document library it's appearing. I have checked that the document properties. The URL is :
https://SharepointSite/:w:/r/sites/demo/_layouts/15/Doc.aspx?sourcedoc={C21982D1-933B-4328-8FA8-3CB8EBDCDDBA}&file=A.docx&action=default&mobileredirect=true
It's open and it's working.
But there's an issue with the folder, the document is not appearing in that folder.
Note:
We don't apply any filter over any views.
We don't apply any permission (Anyone can upload a document)**
I have a page with a thumbnail and I want to remove it and go back to the default image.
I have this values in the config.xml of the content-type
<previewable>true</previewable>
<noThumbnail>false</noThumbnail>
<image-thumbnail>image.jpg</image-thumbnail>
Then I change it to the one I have before
<previewable>true</previewable>
<noThumbnail>true</noThumbnail>
<image-thumbnail></image-thumbnail>
After this, all I got is a broken image link. I don't see the default preview image when I try to create a new content type.
I'm working on 2.5.x on alfresco as my content repository. I did the changes trough Alfresco Share
Am I missing something to pick the change?
Did you try:
admin console -> configuration -> click on “clear cache”.
See attached image.
I have updated column: image_url in [jhi_user] table with different values, and nothing seems to work, example: image_url= ../../../content/media/angular-js.png
Question:
Where in jhipster's file structure should i create a folder to hold user's profiles pictures, and what should the image_url value be so that it works with
<img [src]="getImageUrl()">
It's worth mentioning that this works:
<img src="../../../content/media/angular-js.png">
i created a folder "media" with image: angular-js.png
I am using mysql database and generator-jhipster: "4.6.2"
Thank you for your help in advance
There are 2 kind of images in web apps: the static assets are used for layout (icons, background, logos, ...) they are bundled within your app and the other ones that can be changed without rebuilding your app and which are data.
Static assets can be long term cached by the browser, this is why JHipster uses webpack to version their URLs with a hash code, to modify files that reference them (html, css) and bundle them.
In your design, your image URL is stored in a column of the User entity that points to an avatar image which is a static asset. So webpack is not able to rewrite it.
So either you exclude these images from webpack build process or you store your images as Blobs in your database to enable your users to upload their own images.
Second option would consist in creating a new entity Avatar that holds the Blob and have a one-to-one relationship with User entity. The reason for another entity si that JHipster does not let you modify the User entity.
I exported site from production server (_admin/SiteAndListExport.aspx). All cmp files size is ~8GB. The site uses EBS ( http://technet.microsoft.com/en-us/magazine/2009.06.insidesharepoint.aspx ).
When I try to import that site to my dev environment using command
Import-SPWeb http://dev2:8080 -Path C:\spbackup\site.cmp
I have got error:
Cannot import site. The exported site is based on the template STS#0 but the destination site is based on the template SPS#0. You can import sites only into sites that are based on same template as the exported site.
On DEV environment I created site with "select template later" option.
How to resolve that error?
I would like to speed up exporting and importing site. Is it possible to use some dump EBS provider to ignore all files and attachments stored in EBS?
Is it possible to detect from ISPExternalBinaryProvider implementation that invoking RetrieveBinary method is from export proccess?
I am trying to create an extension ('XML Uploader') with a backend module and a frontend plugin also.
The backend module will be used for managing xml files (upload, validate against a DTD), and the frontend plugin should be used for displaying the uploaded xmls.
The problem is with the frontend part:
I followed
the basic extension tutorial - added a new page, created a content element of type 'Insert plugin' - but when trying to add a new record, the type 'XML Uploader' does not appear in the list of new record types. Moreover, the changes made to class.tx_xmluploader_pi1.php have no effect.
So how should I work with the frontend plugin? Or would it be better to create a separate extension instead?
Any help would be very much appreciated.. Thank you.
When creating your table with the extension kickstarter you must check the "Allowed on pages:" checkbox to allow records from this table to be created on regular pages.
If your changes have no effect, it could be that the page is cached by typo3. In that case you can clear or disable the cache with the admin panel or in the page configuration menu.
You have to include the static template of your extension (I presume you used the kickstarter or extension_builder):
go to the your template, in the object browser you should see something like:
plugin.tx_xmluploader_pi1 = USER
if you can't find it, edit your template (edit/modify => edit whole template record) and add your extension template in the tab 'Includes'
Additionally, check your ext_localconf.php for the line
t3lib_extMgm::addPItoST43($_EXTKEY, 'pi1/class.tx_xmluploader_pi1.php', '_pi1', 'list_type', 0);
This is where your FE plugin is being registered.