mikeotgaar

Same problem here – even when the redirect to ‘next page’ has been created manually.
(Plugin v 1.2)

Also getting this (4 sites using different themes) Plugin ver 1.2

My pleasure. Looking forward to seeing 0.4.
All the best
Mike

Hi aokiiro
This is not a plugin issue. I had a quick look at the source code for the page and it’s HTML markup related.

I see the markup includes both <p style="text-align: center;"> and <img class="aligncenter> for the image element.
Try using only the text-align: center and set the image position to NONE in the the standard WordPress image control. This should prevent the “wrapping” effect you are getting from the syle sheet class.

Note: <br> tags won’t provide enough seperation nor do they end the last markup correctly – so using enter to create line breaks may not be sufficient

Also try adding <p>&nbsp;</p> between lines in HTML (The first item.image on the page has this (one line between Primero photos and the date then 2 lines of <p>&nbsp;</p> which serves to space the text and the images…
You could also use Ultimate Tiny MCE “div clear both” to seperate the items…

I know this solution may not be what you are looking wanting for someone not familiar with HTML markup etc to use. Perhaps you should disable the advanced image control buttons to keep things simpler for your friend.

The bug looks like a theme style sheet/template problem more than anything.

To check this switch to a default wordpress theme e.g twenty eleven and see if the problem goes away… If so then submit a theme bug report – your theme looks like a commercial theme?

Hope this helps – sorry it sounds so technical.

Thanks for fast reply Josh
It’s working fine now – I cannot tell you what the problem was – made no changes to anything – inlcuding cache plugin, or cached files, but re-installed the update today on all site and it’s fine.
By the way – the row selection is a nice feature – will now have to update my article on the plugin…

Got the reason – only a partial fix though.
It has something to do with custom menus with the Mystique theme (and possibly some other 3rd part themes as well – must be something with the code they are using).
Only appears when using a custom menu, not with the default menu.
Interesting, I wonder what is causing it.
The only clue to anything is this message from the theme debugger:
The theme [field] shortcode was disabled because the tag has already been registered by a plugin.
Note: I recreated the Database from a current backup, after deleting all tags and categories manually and running a DB optimiser script. In the process the theme and several plugins were returned to the default state…
At least the error message is gone from public view. If it comes to a choice between custom menus (wanted) and the plugin – the page categories and tags is wanted more!

Hi James – To keep you updated
I only get this now with one site – using Mystique (Ajax version) – it doesn’t do it on another (testing) site using the same theme, so I must assume there’s a plugin conflict
When I get time I will try to replicate this on the testing site – add the same plugins used and settings as the one with the error until the message appears
Will advise further – need to find time to do this.
Mike

Version 1.2.1 Fixed this! Thanks
Will be definitely be using it on some other sites in portfolio as well

Charlie Davidson: I think James meant you should re-install with version 1.2.1 to fix the bug.
Nice that this plugin no longer needs hard coding to work – well done!

Thanks for the info – RE the delay – it happens to all of us!
I’m not using the plugin at the moment – but will try it again in the the (hopefully) not too distant future.
I’ll set it up on a testing site to see if the same happens, with a few different themes, and let you have the details whatever happens. (I just need some time as I’m very busy right now).
If required I can let you log in to the testing site as an admin.
Hopefully you are correct about the CSS/Theme – I like the concept of this plugin…

I second logic52’s comment – Thanks for creating this plugin – It’s getting installed on 3 sites right now

A similar thing for me – WP 3.3 with Mystique Theme.
Form tab not visible an any page.
CSS and JS links are in page source code.

Might be a theme related issue, not WP

“select a post status from a drop-down”
I think it’s a very good idea. Adds a bit more to the plugin features, without hacking into WP core.
It’s great to see these sort of plugins coming into WordPress.

Hi all – FOUND THE PROBLEM

This does not now look like a plugin problem

I sent a mail to Mark – re this problem discovered today (06 Jan 2012
It turns out to be a .htaccess issue possibly not related to the plugin at all – so wanted to let everyone know. Also suggested to Mark he adds something about this to the closed ticket so anyone else who finds this will know.

Somewhere this .htaccess file gets created in the /wp-content/plugins/wp-online-store/admin folder(it’s not in the plugin install package?) and restricts access to the folder with a password requirement – where the referenced /passwd file is not present.

The file seems to be created during a server cron run, definitely not during the plugin installation.

For a temporary fix deleting this file from /wp-content/plugins/wp-online-store/admin folder fixes the problem!

May not be the best way to do it – but works in the meantime until I can find a better way.

Clicked The Works with WP 3.3.1 as well – still a great plugin for e-commerce system. Highly recommended.

Thanks Garfield – did eventually get the update – been very busy 2 weeks.

(To Ray – I’d be interested to know your ISP and server configuration – see if there’s any correlation – I don’t want to turn this support forum into a chat line – mail me [email protected])

Getting this as well – having to re-install every day. Bit of a nuisance as de-activating alone isn’t sufficient to fix the bug – plugin has to be removed completely and re-installed, so all images have to be uploaded again.(Pity about that).

Have tried with Firefox, Chrome and IR8 – all with cleared caches and cookies.

Will try backdating WP on development server in new year and testing there. Having to stop building my site until I find a solution.

Ticket submitted already…