photos
rotnme - June 16, 2009 - 03:18
I'm trying to upload photos. I upload them to icme browser and then import them to the page, all seems well but when I go to the actual page there are no photos. I typed in text along with them and that shows. ???
=-=
ensure you are using an input format that isn't stripping the img tag.
you can view the source code of a rendered page and check whether the tag is actually being printed.
How would I go about this,
How would I go about this, I'm new to all of this. Thanks in advance.
=-=
when it comes to core modules, the best place to gain some information is in adminsiter -> help or here on drupal.org.
see: Core Modules
and directly to filters/input formats = Filter: Input formats for user content
piggyback question - photos today
D 6.12 on WAMP standalone dev system.
Learning about images. I have a directory of jpg's (I can convert them with Photoshop if req'd) that I want to attach to pages in a book so they display with the pages.
I have Image, Image Assist, Image Attach, Image Gallery, Image Import modules in, but can't turn on Image Assist as it wants a Views module. There are 3500+ modules to search through; does anyone know what Views module Image Assist wants? And do i need Image Assist to do this? Seemed good at the time. . .
found
never mind; found it.
I can't figure this
I can't figure this out........... Can anyone kind of walk me thru what they think the problem is. Thanks.
=-=
when creating content, under the text box you have a collpased menu called input formtats. By default the img tag is only available to the FULL HTML input filter. That said, you either have to switch to the FULL HTML input filter, or add the img tag to the FILTERED HTML filter in administer -> input formats.
The idea is that you don't want just anyone allowed to add any kind of tag they want to your site, That said, input formats are a kind of "security" measure that allows you to allow and disallow what tags are exposed on your site regardless of what tags are added by users.
Pardon my inexperience, under
Pardon my inexperience, under input formats I have full html checked. When I go to admin/input formats I have
Filters
Choose the filters that will be used in this filter format.
HTML corrector
Corrects faulty and chopped off HTML in postings.
HTML filter
Allows you to restrict whether users can post HTML and which tags to filter out. It will also remove harmful content such as JavaScript events, JavaScript URLs and CSS styles from those tags that are not removed.
Line break converter
Converts line breaks into HTML (i.e.
and
tags).
URL filter
Turns web and e-mail addresses into clickable links.
html corrector is checked, line break converter is checked, url filter is checked. where is the img tag? Thanks much.
=-=
you don't add tags to FULL HTML because it's full HTML and not stripping html tags. you can add tags to FILTERED HTML by using the configure "tab" after clicking the configure link in administer -> input formats.
to switch an already existing node to FULL HTML you edit the node and expand the collapased menu for input formats and adjust as necessary then resave the node.
rereading the README.txt file in the module download also explains adding the img tag to FILTERED HTML or switching to the FULL HTML input format in the Troubleshooting section.
So confused. I was lacking
So confused. I was lacking the image module. put that in as well as imagefield and image_assist. Put these in and received an error message to the effect that image directory was missing. Fooled with this for a bit using what info I could find here to no avail. Now, as if I was not previously, I am totally confused. All I want to do is upload some picts. I'm losing my mind with this. Please, someone help...............
=-=
originally you stated you were using IMCE, the issue now is, what module is in use?
imagefield, requirs you to build a content type with CCK or add to an already existing content type. Also of note, imagefield and image.module DO NOT work in conjunction with one another in that you cannot add an imagefield to the image content type provided by the image.module.
img_assite provides a simple way to use images but requires you to enable the img_assist filer in your input format.
The issue now is you must choose a single method for adding images and removed the "other" modules you've installed with regards to images. At that point we can walk you through a process to use the module you choose provided you tell us exactly what module you've chosen to keep and employ to handle images.
Whew.....
Whew.....
Enabled Name Version Description
Administration menu 6.x-1.4 Provides a dropdown menu to most administrative tasks and other common destinations (to users with the proper permissions). **CHECKED**
CCK
Enabled Name Version Description
Content 6.x-2.3 Allows administrators to define new content types. **CHECKED**
Required by: Content Copy (enabled), Content Permissions (enabled), Fieldgroup (enabled), FileField (enabled), ImageField (disabled), Node Reference (enabled), Number (enabled), Option Widgets (enabled), Text (enabled), User Reference (enabled), FileField Meta (disabled)
Content Copy 6.x-2.3 Enables ability to import/export field definitions. **CHECKED**
Depends on: Content (enabled)
Content Permissions 6.x-2.3 Set field-level permissions for CCK fields. **CHECKED**
Depends on: Content (enabled)
Fieldgroup 6.x-2.3 Create display groups for CCK fields. **CHECKED**
Depends on: Content (enabled)
FileField 6.x-3.0 Defines a file field type. **CHECKED**
Depends on: Content (enabled)
Required by: FileField Meta (disabled), ImageField (disabled)
FileField Meta 6.x-3.0 Add metadata gathering and storage to FileField. **NOT CHECKED**
Depends on: FileField (enabled), Getid3 (missing), Content (enabled)
ImageField 6.x-3.0 Defines an image field type. **NOT CHECKED**
Depends on: Content (enabled), FileField (enabled)
Node Reference 6.x-2.3 Defines a field type for referencing one node from another. **CHECKED**
Depends on: Content (enabled), Text (enabled), Option Widgets (enabled)
Number 6.x-2.3 Defines numeric field types. **CHECKED**
Depends on: Content (enabled)
Option Widgets 6.x-2.3 Defines selection, check box and radio button widgets for text and numeric fields. **CHECKED**
Depends on: Content (enabled)
Required by: Node Reference (enabled), User Reference (enabled)
Text 6.x-2.3 Defines simple text field types. **CHECKED**
Depends on: Content (enabled)
Required by: Node Reference (enabled), User Reference (enabled)
User Reference 6.x-2.3 Defines a field type for referencing a user from a node. **CHECKED**
Depends on: Content (enabled), Text (enabled), Option Widgets (enabled)
Core - optional
Enabled Name Version Description
Aggregator 6.12 Aggregates syndicated content (RSS, RDF, and Atom feeds). **NOT CHECKED**
Blog 6.12 Enables keeping easily and regularly updated user web pages or blogs. **NOT CHECKED**
Blog API 6.12 Allows users to post content using applications that support XML-RPC blog APIs. **NOT CHECKED**
Book 6.12 Allows users to structure site pages in a hierarchy or outline. **NOT CHECKED**
Color 6.12 Allows the user to change the color scheme of certain themes. **CHECKED**
Comment 6.12 Allows users to comment on and discuss published content. **CHECKED**
Required by: Forum (disabled), Tracker (disabled)
Contact 6.12 Enables the use of both personal and site-wide contact forms. **CHECKED**
Content translation 6.12 Allows content to be translated into different languages. **NOT CHECKED**
Depends on: Locale (disabled)
Database logging 6.12 Logs and records system events to the database. **CHECKED**
Forum 6.12 Enables threaded discussions about general topics. **NOT CHECKED**
Depends on: Taxonomy (enabled), Comment (enabled)
Help 6.12 Manages the display of online help. **CHECKED**
Locale 6.12 Adds language handling functionality and enables the translation of the user interface to languages other than English.
Required by: Content translation (disabled) **NOT CHECKED**
Menu 6.12 Allows administrators to customize the site navigation menu. **CHECKED**
OpenID 6.12 Allows users to log into your site using OpenID. **NOT CHECKED**
Path 6.12 Allows users to rename URLs. **CHECKED**
PHP filter 6.12 Allows embedded PHP code/snippets to be evaluated. **NOT CHECKED**
Ping 6.12 Alerts other sites when your site has been updated. **NOT CHECKED**
Poll 6.12 Allows your site to capture votes on different topics in the form of multiple choice questions. **NOT CHECKED**
Profile 6.12 Supports configurable user profiles. **NOT CHECKED**
Search 6.12 Enables site-wide keyword searching. **NOT CHECKED**
Statistics 6.12 Logs access statistics for your site. **NOT CHECKED**
Syslog 6.12 Logs and records system events to syslog. **NOT CHECKED**
Taxonomy 6.12 Enables the categorization of content. **CHECKED**
Required by: Forum (disabled)
Throttle 6.12 Handles the auto-throttling mechanism, to control site congestion. **NOT CHECKED**
Tracker 6.12 Enables tracking of recent posts for users. **NOT CHECKED**
Depends on: Comment (enabled)
Trigger 6.12 Enables actions to be fired on certain system events, such as when new content is created. **NOT CHECKED**
Update status 6.12 Checks the status of available updates for Drupal and your installed modules and themes.
Upload 6.12 Allows users to upload and attach files to content. **CHECKED**
Core - required
ImageCache
Enabled Name Version Description
ImageAPI 6.x-1.6 ImageAPI supporting multiple toolkits.
Required by: ImageCache (enabled), ImageCache UI (enabled) **CHECKED**
ImageAPI GD2 6.x-1.6 Uses PHP's built-in GD2 image processing support. **CHECKED**
ImageAPI ImageMagick 6.x-1.6 Command Line ImageMagick support. **NOT CHECKED**
ImageCache 6.x-2.0-beta9 Dynamic image manipulator and cache. **CHECKED**
Depends on: ImageAPI (enabled)
Required by: ImageCache UI (enabled)
ImageCache UI 6.x-2.0-beta9 ImageCache User Interface. **CHECKED**
Depends on: ImageCache (enabled), ImageAPI (enabled)
Other
Enabled Name Version Description
Advanced help 6.x-1.2 Allow advanced help and documentation. **CHECKED**
Required by: Advanced help example (enabled)
Advanced help example 6.x-1.2 A example help module to demonstrate the advanced help module. **CHECKED**
Depends on: Advanced help (enabled)
IMCE 6.x-1.2 An image/file uploader and browser supporting personal directories and user quota. **CHECKED**
Required by: IMCE Wysiwyg API bridge (enabled)
Transliteration 6.x-2.1 Provides transliteration for UTF-8 text input and sanitizes file names. **NOT CHECKED**
User interface
Enabled Name Version Description
IMCE Wysiwyg API bridge 6.x-1.0 Makes IMCE available as plugin for client-side editors integrated via Wysiwyg API.
Depends on: IMCE (enabled), Wysiwyg (enabled) **CHECKED**
Wysiwyg 6.x-2.0 Allows users to edit contents with client-side editors. **CHECKED**
Required by: IMCE Wysiwyg API bridge (enabled)
Views
Enabled Name Version Description
Views 6.x-2.6 Create customized lists and queries from your database. **CHECKED**
Required by: Views exporter (enabled), Views UI (enabled)
Views exporter 6.x-2.6 Allows exporting multiple views at once. **CHECKED**
Depends on: Views (enabled)
Views UI 6.x-2.6 Administrative interface to views. Without this module, you cannot create or edit your views.
Depends on: Views (enabled) **CHECKED**
Thank you.........
=-=
I have no idea what ou want me to do with that list ???
sorry, this is my module list
sorry, this is my module list showing what is enabled (**CHECKED**). hoping this would aid you in seeing what i have going on.
=-=
I can't choose the method you want to use for images. You must do that and we can help you implement the method you choose.
At this point your original question was about how to get images to show with IMCE and now you've thrown multiple image handling modules in the mix.
It does me or you, no good for me to explain to you how to build a content type and use imagefield if that isn't the way you want to go.
You should take the time to research the image handleing modules. Read their README.txt files, their project pages and look for tutorials using google. To narrow down how you want images to be handled.
If you still have issues after doing so, List here the module you've chosen and fully explain your desires. Elaborating as much as possble, as statements like "I just want images to show" doesn't help much because I can tell you to hardcode images in content but that may also not be your best option depending on what you want to do.
I want to use IMCE, and
I want to use IMCE, and thought I was. Somehow I got confused and brought in other mods that I don't need apparently. All I'm looking to be able to do is, for example on my home page I have a logo, a brief text statement and below that I want a photo. Ditto for the about us page, text with photos, a gallery page showing off different project photos. I was thinking that I would be able to create a page, insert text and using the tool bar (insert/edit image i think) then choose an uploaded photo and bring it to the page. Where have I gone wrong?
=-=
For the gallery I would employ the image.module and not IMCE. (nothing against IMCE) but if you are the only person using the site, IMCE really isn't necessary. image.module has a gallery module packaged with it. This will handle your image needs as far as that is concerned.
As far as an image under the logo on the front page. That is something you will likely want to do at the theme level or using your mission statement region. Of course this depends on exact placement and the theme layer will give you far more control where that is concerned. I've not seen your site and can't read minds : ) to envision exactly what you see in your head.
all these tools that you want to "bring" into the site may not be making things any easier for you. I assume you are looking for the most simple way to accomplish these tasks, but they must be handled one at a time.
I've already given you a method for handling an image.gallery. image.module allows images to be saved as nodes. I think I'd take the time to investigate the img_assist module and the imagebrowser.module.
you state you want images to appear in these places, but you don't state if they should be thumbnails, or anything like that so you will also have to make those decisions.
I know this is frustrating and developers are working toward combining development toward an image handling system in core. Until that time though, you are sort of stuck with image handling hell.
My best advice is to start a test site Where you can work with these modules away from your already existing work. Testing the image handling methods, learning them, what they do, don't do what they work with, don't work with. Once you begin to understand how the modules work and don't work you can progress toward a final solution.