Thread

ExpressionEngine version 2.1.3:20101220 - btw; I’m making the assumption EE2 works with browsers (Safari, Chrome and Firefox) on OSx 10.6.x. I have Flash turned off on my system but Chrome has it’s own Flash render engine built it.

My guess is that either there’s an issue with the browser or the installation and if the issues with the installation it must be an upgrade rather than cold-start issue. Or, quite possibly because I can’t hear myself think over the sound of my own teeth gnashing ... 😉

How do I configure HTML buttons for Publish and Edit?

I do understand that I need to either setup HTML Buttons globally then on a per user basis. I have done this but the bottoms do not appear on the Publish or Edit pages. The documentation implies the existence of a Write Mode (initiated by clicking on the Pencil Icon) - as I have no pencil icon is that the answer?

Maybe not because the documentation tells me I’ll also notice “Check Spelling”, “Glossary”, and “Smileys” options beneath each field - I have a file upload button too - where does that come from?

How do I upload files and get meaningful content in a Publish or Edit page?

As I say above, each field has a file upload button below it. When I click I get an idiot box offering options to upload and image/file or select an image/file from the file upload directory.

I each case I next get a dialog box asking me for a link then for alt text. The link it is asking for is the attribute for the src element rendering the whole box, in fact the whole process, redundant (if I know the src why not simply write the tag manually?)

Your kind observations are much appreciated (unkind ones too, probably).

Regards, Jules

I resolved the How do I configure HTML buttons for Publish and Edit? issue by going field by field (100’s of them ... 😉 and turning formatting on. It appears the upgrade script takes an ultra-conservative view. Daft really.

EE appears to have a default setting for files and images formatting buttons and for its own file manager as follows;

link =>

<a href="[![Link:!:http://]!]" title="[![Title]!]">

file =>

[![Link:!:http://]!]

Why does the file manager require a link rather than select the already selected item?

Which begs the following comment about file types;

I see that I can have a folder to upload files to. I can specify for that folder whether to allow only image or all file types.

Then I can set up a field with type =  Files. I can specify for that field whether to allow only image or all file types.

So what’s the function of a Files fieldtype when I can use a text input field and activate the file manager to create the same effect, other than to allow me to create an inherent conflict by setting the files fieldtype to all files and the upload folder to image only?

Can anyone throw any light on this, please?

Jules

So what’s the function of a Files fieldtype when I can use a text input field and activate the file manager to create the same effect, other than to allow me to create an inherent conflict by setting the files fieldtype to all files and the upload folder to image only?

It’s another method for displaying a file. When end users want more fine grained control of file uploads inside of an entry, I have them use the file upload button inside of a textarea.

If they want to just have an image separate from the main content, I use a File fieldtype.

Does that help?

Hi Jules,

Let’s start with the image link issue. This one I can’t replicate in the 2.1.4 beta; when I select an image I’m only prompted for the alt tag. Is trying 2.1.4 an option for you?

So what’s the function of a Files fieldtype when I can use a text input field and activate the file manager to create the same effect, other than to allow me to create an inherent conflict by setting the files fieldtype to all files and the upload folder to image only?

It’s another method for displaying a file. When end users want more fine grained control of file uploads inside of an entry, I have them use the file upload button inside of a textarea.

If they want to just have an image separate from the main content, I use a File fieldtype.

Does that help?

No, not really Sue. This relates to an anecdotal observation and misses the essence of the question.

Regards, Jules

Hi Jules,

Let’s start with the image link issue. This one I can’t replicate in the 2.1.4 beta; when I select an image I’m only prompted for the alt tag. Is trying 2.1.4 an option for you?

Thanks Brandon,

As part of a wider experiment (Q: What is the real payload of upgrading EE1 to EE2? - something I should reasonably done before I started ... ) I created a new account on my server and installed EE1.7.0 making one or two changes as I went - I did a search and replace on ‘default_site’ (to default_weblog) and changed the system and themes folder names. The site worked.

I then backed up the EE1 database, created a new database and loaded the tables. I installed EE2, renamed the index.php file and ran the upgrade. Essentially I now have two versions of EE running identical content (one from index.php and the other from renamed_index).

I made two observations from this;

1. there’s a heavy payload in upgrading to EE2 (writing default_channel back to default_weblog, HTML buttons, et al); in all it took over four hours to get EE2 to match EE1; and,

2. on an identical server using an identical version of EE (v2.1.3) and identical java clients (OSX-based) the File Manager button did work in the manner you describe.

From which I conclude;

3. the cost of me upgrading any but the smallest of sites is unjustifiable; and,

4. I need to dump the current upgrade to my client’s site and start again from scratch using the database backup. This will eliminate the possibility of corrupted files/scripts (I used “auto” to manage the ASCII/Binary distinction on upload - not always 100% reliable); and if that fails to resolve the issue roll back to v1.7.x and be done.

It would help if I knew which files and folders to target first (ie those responsible for the File Manager) but I’m guessing it’s not as easy as all that.

It would help if I knew which files and folders to target first (ie those responsible for the File Manager) but I’m guessing it’s not as easy as all that.

Hi, Jules. You mentioned in a different thread that you used Transmit to FTP. I’ve seen quite a few cases here where Transmit didn’t upload files correctly, or even skipped some.

In your case, I recommend replacing ALL of your files, using FileZilla which is a cross platform FTP program (free).

I understand this is painful for you, and certainly not the most pleasant way to upgrade.

It would help if I knew which files and folders to target first (ie those responsible for the File Manager) but I’m guessing it’s not as easy as all that.

Hi, Jules. You mentioned in a different thread that you used Transmit to FTP. I’ve seen quite a few cases here where Transmit didn’t upload files correctly, or even skipped some.

In your case, I recommend replacing ALL of your files, using FileZilla which is a cross platform FTP program (free).

I understand this is painful for you, and certainly not the most pleasant way to upgrade.

Hi Sue,

Yes we’ve gotten to the point where we blame Transmit (and later cPanel) before. The main challenge is Transmit v3’s emphasis on sync’ing - if it’s not set up sync to a local directory it places a copy of each file in a local cache (you can trap this if you’ve Growl installed). each time a file’s called it tries to use the local cache and this can create confusion.

Generally I’m a bit ahead of that and in most cases create a local zip archive of all my files and upload then decompress on the server. I always delete files before replacing them for this reason (to flush the local cache).

If I replace the files today this’ll be the fifth time on this installation.

Jules

It would help if I knew which files and folders to target first (ie those responsible for the File Manager) but I’m guessing it’s not as easy as all that.

Hi, Jules. You mentioned in a different thread that you used Transmit to FTP. I’ve seen quite a few cases here where Transmit didn’t upload files correctly, or even skipped some.

In your case, I recommend replacing ALL of your files, using FileZilla which is a cross platform FTP program (free).

I understand this is painful for you, and certainly not the most pleasant way to upgrade.

Okay Sue, I’ve done the upload of system (only) and nothing’s changed. Not sure how good the attached image is but you can see what it does to the img src=”” element if I follow the process through. My guess is that part (or the whole) of a script is simply not running.

Jules

It would help if I knew which files and folders to target first (ie those responsible for the File Manager) but I’m guessing it’s not as easy as all that.

Hi, Jules. You mentioned in a different thread that you used Transmit to FTP. I’ve seen quite a few cases here where Transmit didn’t upload files correctly, or even skipped some.

In your case, I recommend replacing ALL of your files, using FileZilla which is a cross platform FTP program (free).

I understand this is painful for you, and certainly not the most pleasant way to upgrade.

Sue, I also noticed that once the File Manager is called the page cannot load correctly, there are always an un-loadable item ‘about:blank’ - it goes on until about 124 of 125 then stalls there.

See image attached

Hey Jules, looks like this one is resolved (per the other thread) so going ahead and closing. We’ll continue over there. Thanks!