Forum Post : Re: Re: Re: Not Seeing an Import Tool
Up one levelI believe I know what the issue is and I have a solution which worked for me.
In Plone 2.5 the Upload File mechanism is disabled by default.
According to Plone, an update in version 2.5 was a security precaution:
"- Disabled the RichWidget file upload field using CSS. The reason is that it causes a lot of problems for naive users, who upload Word documents, images etc here. The content has to be in HTML or the selected text format for this to work. If you want to re-enable this in your site, add the following to your CSS file: .fieldUploadFile { display: block }"
The CSS file to be modified to enable uploads is public.css. It can be reached through the Zope admin.
Go to Plone/portal_skins/plone_styles/
Double-click public.css to save a copy (goes to the Custom folder by default).
Edit the copied public.css file and change the text:
.fieldUploadFile { text-align: right; margin-right: 0.75em; display: none; }
To:
.fieldUploadFile { text-align: right; margin-right: 0.75em; display: block; }
Then the composite CSS files need to be recompiled.
In the same Zope admin tool, go to:
Plone/portal_css
Under the tab "CSS Registry" click Save.
To verify that the new CSS is being used, go to the public section of your plone site, view the source on any page, and search for the first CSS page in the source. It should have the syntax:
Open that URL in a browser and search for the text "fieldUploadFile"
If it now shows "Block" instead of "none" then you have successfully modified the CSS. If not, start with a fresh browser to make sure the old CSS page isn't being referenced. You can also see that a new composite CSS page is being generated because the CSS page will have a new number (ie. ploneStyles####.css).
Once that "fieldUploadFile" has been changed to "Block" you should now be able to see a browse option under [Step 2: upload file]
Note: One downside to this approach is that the global CSS file has been modified, opening uploads to the whole Plone site. A better solution would be to create a new CSS entry that is only referenced by the ArcheCVS product.