Plugin Author
Ko Min
(@tristanmin)
Hi summitlake,
Sorry to hear that but I’ve fixed that issue in my new version (1.2).
Thanks
Thanks, but still not resolved for me: no change from my post on 1.0. I found the screenshots but cannot tell when one would expect to see them. Does 1.0-1.2 capture the most recent 5 or more existing multisite posts going back to before installation/update, or should the user expect to see results only on new posts after installation/update?
Plugin Author
Ko Min
(@tristanmin)
Hi there,
The way the plug-in work is grab all the posts from the all blogs no matter what they are posted before the plug-in install then put them into the mysql view table and sort them base on the posted dates.
Are you using wordpress 3.0 multisite or wordpress MU?
Thanks
Using WP 3.01 multisite … if there is supposed to be a table with the string ‘view’ in the name, there is no such table in my mysql installation.
Plugin Author
Ko Min
(@tristanmin)
Hi,
Actually, view is not the table name. It is mysql view type table.
In your DB, there should be a table name called your table prefix + ms_posts. If you didn’t change the table prefix when you installed your wordpress, table name will be wp_ms_posts.
Thanks
My posts tables are wp_posts, wp_2_posts, wp_3_posts thru wp_10_posts. No table at all has an _ms_ in the string.
I see you are hard coding your mySQL query for [base_prefix.”ms_posts.*]. So this would not work for me.
I’m not having any other issues operating my single 3.0 multisite installation (replacing 10 separate older 2.9 installations), so it appears my installation isn’t compatible with the configuration you are developing with.
I’ve been posting my multiple-site WP post excerpts manually on the “home” page for years now, and it’s not really that inconvenient. It just seemed that it would be neat if an aggregator could take over the chore.
Thanks.
Got the same problem..
My posts tables are also: wp_posts, wp_2_posts, wp_3_posts and so on… No _ms_ in the string for me either. How could i change that? Would love to use this plugin!
Plugin Author
Ko Min
(@tristanmin)
Hi,
It is a little bit difficult to sort it out because my plugin works well on my client sites even with different configurations.
Obviously I can’t access your database so I can’t tell what is giving you such a problem. Are there any error message or something?
200+ users downloaded my plugin and they never rated my plugin or wrote any feedback so I can’t not tell my plugin is working well or not on their sites.
I will also look into it again. At the same time you try to deactivate one of your blogs (not the plugin) and reactivate it again.
Thanks!
200 downloads and no feedback is discouraging. Whether or not a plugin meets all expectations, users should certainly take a minute to share feedback with open source authors.
I did research this before I found and tried your plugin. I was not expecting it could be done with a plain 3.0 installation (no buddypress, no related parallel installations). But I knew I could be wrong.
I would have to set up a test blog and then deactivate _that_, but to be honest, I currently still just copy and paste excerpts by hand, so I uninstalled the plugin.
Instead, please, let me ask you this: is your plugin designed to work under a brand-new 3.0 installation configured for multisite, 2+ blogs on a single database, and NO other plugins or support apps?
All I did for 3.0 MS is follow the how-to’s which resulted in the table naming we already discussed. I’m not delighted with it (strange permalinks) but it works flawlessly. And, Google and my readers are using published permalinks.
It could take a lot of work to reconfigure a 10-blog site for a new table name (table prefix + ms_posts). This would probably change all the permalinks. As a “drop table” situation with a powerful text editor, this brings a lot of high-risk change with possible downtime.
So, it would be better if the plugin can work with the standard table names we have now.
Can you tell us why there would be two different naming conventions and where the _ms_ naming scheme originally came from?
Thanks — Alex
Plugin Author
Ko Min
(@tristanmin)
Instead, please, let me ask you this: is your plugin designed to work under a brand-new 3.0 installation configured for multisite, 2+ blogs on a single database, and NO other plugins or support apps?
Yes! It is. I’ve developed this plugin using brand-new wordpress 3.0 multisite enabled.
It could take a lot of work to reconfigure a 10-blog site for a new table name (table prefix + ms_posts).
Plugin will create only one table named (table prefix)+ms_posts (normally it is wp_ms_posts). Table type is “views” type (virtual table)
Can you tell us why there would be two different naming conventions and where the _ms_ naming scheme originally came from?
ms came from the plugin name “multisite”. Like the other pulgins do (e.g NextGen Gallery plugin creates wp_ngg_album)
There were several different “how-to’s” posted of varying clarity. Perhaps some of us picked one using the different table naming scheme we discussed. Not knowing if the recommended naming scheme also had to match hard-coded 3.0 multisite requirements, we would have just used what our particular “how to” recommended.
As to your question about error messages, I never saw any browser errors. I don’t remember if I checked the server error log, but I’m pretty sure I would have.
You asked about table names earlier. Apologies for the post length, but my database and table names wp_ through wp_10_ are listed below (wp_4 thru wp_9 omitted for brevity):
wp_1 (108)
wp_2_commentmeta
wp_2_comments
wp_2_links
wp_2_options
wp_2_postmeta
wp_2_posts
wp_2_terms
wp_2_term_relationships
wp_2_term_taxonomy
wp_2_weatherxml
wp_3_commentmeta
wp_3_comments
wp_3_links
wp_3_options
wp_3_postmeta
wp_3_posts
wp_3_terms
wp_3_term_relationships
wp_3_term_taxonomy
wp_3_weatherxml
….
wp_10_commentmeta
wp_10_comments
wp_10_links
wp_10_options
wp_10_postmeta
wp_10_posts
wp_10_terms
wp_10_term_relationships
wp_10_term_taxonomy
wp_10_weatherxml
wp_blogs
wp_blog_versions
wp_commentmeta
wp_comments
wp_links
wp_options
wp_postmeta
wp_posts
wp_registration_log
wp_signups
wp_site
wp_sitemeta
wp_terms
wp_term_relationships
wp_term_taxonomy
wp_usermeta
wp_users
wp_weatherxml
Hi, I love this plugin and it worked great for me before I upgraded to wordpress 3.1 (I find myself typing these lines a lot!)
No only the heading shows up and no posts.
This was a really nice functionality, which is very basic to a multisite/multiuser blog
