If you use TinyMCE in your Content Management System (CMS) projects, you no doubt also give clients the ability to add images and links to their content with TinyMCE's Link and Image buttons. But by default, these popup windows come with a variety of fields into which unsuspecting clients can input values which will translate into unwanted code when delivered to the page.
- The client specifically asked for AJAX to be used.
Which is better in links from the search engines' point of view: plain text or images with an
alt attribute that says the same thing? For example, is
<a href="">This is a link</a> better than
<a href=""><img alt="This is a link" src=""></a>?
I have come across a few little solutions/fixes recently to various problems I've encountered when building sites with ExpressionEngine (EE) that I thought it would be worth sharing. A couple of these were tips I picked up from other posters on the EE forums and the third was one I came up with myself to solve a particular problem I had.
The problem with this method however is that it uses a large negative
text-indent to remove the default text from screen, and with images turned off in the browser, you don't see anything. This has accessibility implications not only from the perspective of those with disabilities, but also for those who deliberately turn images off, i.e. people on slower connections or those using handheld devices who are trying to limit the amount of information downloaded to their phone.
If you're using ExpressionEngine (EE) with a WYSIWYG editor, chances are you're using either TinyMCE or FCKEditor. I myself use TinyMCE and it seems like a lot of people prefer it to FCKEditor, but for one thing – it doesn't have good image and file management capabilties built in by default.
A while ago I wrote about some of the extensions I use with Firefox which make the job of web development easier. I've since added some new ones to Firefox that I use on a fairly regular basis, so thought I should update the list.
For the article I wrote recently on web design galleries, I compiled a table of the galleries in a MySQL database. To be able to display the table and the associated charts and other statistics that went with it, I needed to be able to connect to this external database from within Wordpress.
Recently I had to add basic shopping cart functionality to a site that had been built with ExpressionEngine (my CMS of choice). “No problem,” I thought; I can use the Simple Commerce Module (SCM), which as the names suggests, is ideally suited to simple ecommerce requirements, and which I had used before on other EE sites.