gr1zzly

+ 1 for “Uncaught TypeError: Cannot read property ‘currentStyle’ of null” JavaScript error relating to WPUF loading with plupload.

Specifically I am seeing this error on the ‘edit’ page, I am using WPUF v1.2.3.

The strange thing is that when I click “Add another” to upload another attachment the popup file window does appear, and appears (uhuh) to work — and so therefore I assume ‘plupload’ is working.

The trouble is it appears to have killed the post_content editor’s “Add media” button — clicking this now does nothing!

I found the following lurking in my html head, but I can’t seem to find out where this is being loaded from (i.e. where it is being enqueued or attached to an action hook such as ‘wp_head’?!)

var wpuf_attachment = {"nonce":"dba594863a","number":"6","attachment_enabled":"1","plupload":{"runtimes":"html5,flash,html4","browse_button":"wpuf-attachment-upload-pickfiles","container":"wpuf-attachment-upload-container","file_data_name":"wpuf_attachment_file","max_file_size":"2097152b","url":"http:\/\/local.snip-domain.co.uk\/wp-admin\/admin-ajax.php?action=wpuf_attach_upload&nonce=8ff3a39f9b","flash_swf_url":"http:\/\/local.snip-domain.co.uk\/wp-includes\/js\/plupload\/plupload.flash.swf","filters":[{"title":"Allowed Files","extensions":"*"}],"multipart":true,"urlstream_upload":true}};
/* ]]> */

…is this relevant?

Hi Ron,

It’s never a good idea to edit a ‘base’ file for a plugin (or WordPress itself) because if/whenever you update it your changes will be over-written and you’ll have to edit the file again. Instead it is better to implement the changes you require in a way that over-rides the ‘default’ *thing* you’re trying to change (i.e. in another file which supersedes the one you want to change).

In the case of styles this should be easy since CSS is ‘cascading’ in it’s nature and so has a logical over-ride syntax structure. Which means that in order to over-ride the default styles in the plugin you simply need write a ‘heavier'[1] style rule, and make sure that it is loaded after the plugin’s styles.

Since plugin’s are set up before the active theme then any style-sheet loaded by your theme should work to over-ride the plugin styles. — FYI the WPUF plugin uses the ‘wp_enqueue_style’ action hook.

[1] Note: ‘heavier’ means a more specific rule (based on CSS’s rule weighing metrics, e.g.#IDs ‘weigh’ more than .classes, which weigh more than <elements>). The best way to increase weight is to increase selector specificity, usually by adding an appropriate #ID.

If you are struggling to achieve an over-ride then, at a push, if you absolutely have to, you can use the ‘!important’ suffix to ‘force’ an over-ride on the appropriate style rule(s), but this is best avoided if possible!

hth

These are my top “Helping myself” resources when I’m working with WordPress:

The Loop – The Loop out puts all of your posts data to the page so understanding this is key!

Template Tags – WordPress’ Template Functions (use within “The Loop” !)

Function Reference – A guide to WordPress’ built in PHP Functions.

Writing a Plugin – Help creating your own Plugins for WordPress.

Widgets API – For help when creating your own widgets, or adapting a plugin into a widget.

As you’ll see the codex here is pretty comprehensive and with a reasonable knowledge of (X)HTML and PHP (plus CSS for styling of course) there’s everything you need to get you started with customising and developing your own templates, functions and plugins etc. for WordPress.

hth

How are you with CSS? In styles.css try:

.post {
border-left:1px solid #ddd;
float:left;
padding:0 12px;
width:50%;
}

.post:nth-child(odd) {
border-left:none;
}

I haven’t tested this but off the top of my head this should give you two posts side by side with a faint grey line in between them. The padding makes sure that there is a gap between the content of the post and the line, while the second rule prevents the left hand side posts from also having a left border.

Of course you could add whatever styling you want with CSS, if you’d prefer not to have a vertical border between the posts etc.

This is most likely the easiest way without customising a template file for this purpose. Hopefully it should at least get you somewhere near.

If your not sure how to edit styles.css:
You can access styles.css in the admin panel’s theme editor, just select the file from the right hand list, scroll to the bottom of the file and paste the code there.

Worst comes to worst and my code doesn’t work simply edit the file again and delete what you just pasted!

hth

The permalinks are only applied after the root domain part of the URL (edit – well actually after the ‘root’ URL for the WordPress installation!). So what you’ve effectively done (i’m guessing) is create a permalink structure that equates to…

“http://www.lebronnewsonline.com/lebronnewsonline.com&#8221;

..or something like that.

One way I can think of to fix this would be to edit the WordPress database directly using phpMyAdmin, which you may have available under you hosts domain control panel.

1. Open phpMyAdmin and select the relevant WordPress database –
this should should be something like “your domain name” OR “your domain user name” underscore ( _ ) “whatever you called your WordPress blog”.

2. Once you’ve clicked on the database name it’ll show you the tables within that database. You need to select the “wp_options” table and then the “browse” tab.

3. Find the row with the “option_name” of “permalink_structure” –
this should be at the top of page 2 so just click on the Next “>” button above the table results.

4. Click on the pencil (“Edit”) icon to the left hand side of the row and delete the text in the “option_value” field then click “Go” to save the changes.

Leaving this field blank should return WordPress to it’s default “ugly” URL’s and hopefully get the site working again. You’ll be able to edit the permalink structure again within the WP admin panel. Possibly after reading this.

hth

If there isn’t an option to do so in the themes settings (if it has an Admin page!) then you’d have to edit the template files directly – Of course then it’ll depend on which ‘pages’ you want them removed from e.g.: Posts, Pages, Archives, Categories, Tags etc. can all have their own template file with unique code in. Or possibly just the ‘loop.php’ file with themes in a Twenty Ten style!

The function to look for in the code is the_tags(), simply delete this piece of code. OR it may be safer to just comment it out with either:

// Double forward slash marks a single line comment
# As does the hash or pound sign as it's sometimes called
/* for multi-line comments
use a slash star....
....star slash combination*/

These must all occur within the <?php ?> tags

— better late than never —

Hi, I had a look at the other post you’d linked to and I can see why you couldn’t exactly follow it, I think they were making it more complicated than it needs to be.

Here’s the code I’ve just written to do the same job:

<?php /* The Loop */ ?>
<?php $post_counter = 0;
while ( have_posts() ) : the_post() ?>
	<?php $post_counter++; ?>
	<div id="post-<?php the_ID(); ?>" <?php if( $post_counter == count( $posts ) ) post_class('last-post'); else post_class(); ?>>

The conditional statement simply test IF the $post_counter has reached the same number as the total counted posts, you can then call the post_class() function with or without any additional class as needed. You can add as many classes as you like this way, just comment them and comma separate!

hth