Manuel Schmalstieg

Ok, then I guess the issue is resolved ??

Thanks Scribu for the splendid x-mas holiday support.
I will give the template parameter a try.

I just noticed that someone filed a ticket on this matter two weeks ago:

https://core.trac.www.ads-software.com/ticket/19541

So there’s hope that things will be fixed in WP 3.4 ??

Indeed, somebody pointed this out already in the plugin author’s forum, whith some instructions on how to fix it:

https://plugins.webdevstudios.com/support/topic/flyout-menus-in-wp-3-3/

Is your theme customized for displaying your custom post type?

If you are using a regular off-the-shelf theme, your theme probably displays only posts and pages. You would need to modify the theme, so that it can show your new custom post type. For more information about how to achieve that, follow the links at the bottom of https://codex.www.ads-software.com/Post_Types

It works perfectly well on my side with the current WordPress (3.3).

Les retours seront notamment bienvenus concernant les éléments suivants:

ligne 361 et 497:
msgid “Whatcha’ up to?”
msgstr “Quoi de neuf?”

ligne 445 :
#: inc/options-page.php:161
msgid “Post prompt:”
msgstr “Message d’avertissement:”

J’ai aussi d? choisir une traduction pour le nouveau post type “Status Update”, qui n’existait pas dans la localisation précédente. Je l’ai traduit par “actualité”.

ligne 577:
msgid “Status Update”
msgstr “Actualité”

MarieDi,
You might be happy to know that I did a new French translation for P2 (version 1.3.3).

You will find it in this thread:
https://www.ads-software.com/support/topic/theme-p2-new-french-locale-nouvelle-localisation-francaise

Glad to know that this brilliant solution was useful for someone ??

Same issue here. Either we did some non-obvious mistake during setup, or Twitter has changed something.

For instance, the plugin told me to setup the application as “browser” type, but I have not seen that option. It’s not offered anywhere in the Twitter application settings.

About the callback URL, what should that be? The URL of the WP site?

EDIT: Answering my question, it seems that this worked, entering my WP site URL into the “callback URL” field allowed the plugin to authenticate itself.

Got some feedback from the list!

For the time being, there is an advanced upload plugin that can help – it has client-side resizing capacity:
https://www.ads-software.com/extend/plugins/wplupload/

According to @ottodestruct, Plupload will be integrated into WordPress 3.3. How cool is that? ??

No, unfortunately I didn’t.

I guess we should either post the question on the [wp-hackers] mailing-list, or open a feature request in trac.

Thanks indeed! The Jetpack admin interface gave me the impression that there was no way to disable this functionality (it only has a “Learn more”, but no “Configure” button). The trick: when you click “Learn more”, the “Deactivate” button shows up ??

Versions used: Jetpack 1.1.3, WordPress 3.2.1.

Indeed, it looks like the pagination function doesn’t fully “get” that the posts_per_page parameter has changed.

Let’s say for instance that i have a category with 50 posts, and have set the default limit to 20. If i am on the category page, that would result normally in 3 paginated pages (20 + 20 + 10).

Now, if we add a “posts_per_page=5” to the query for this category page, the pagination will show 10 pages, which seems logical (10*5 = 50).

The 3 first pagination links will work fine, but the following ones will result in a 404 page. It looks like at some place in the command chain, the system still thinks that there are only 3 pages rather than 10.

A smart fix for this would be highly welcome — for now i simplify my life by using the default posts_per_page on all paginated pages, and using custom posts_per_page values only when there’s no pagination needed …

Same issue here, running WP 3.1-RC2-17258. I wanted only the medium size to be regenerated, but after doing so the connection to thumbnail sizes seems to be “broken” (so instead of thumbnails the full size was loaded). The images are still there, but for some reason WP isn’t aware of the older sizes.

So it seems that we have to rebuild all images (which is also what the “Regenerate Thumbnails” plugin is doing). Maybe a limitation of the internal WP thumbnail function?

Happy to see that the issues are already fixed in today’s 3.1-beta1-16884 !