ParanoidSardine

I’ll give that a try. I have two situations, one in which I want to get all posts and another where I needed posts of with a specific category. I will check into query_posts to see what I get.

I will play by the rules, but my basic question of why the loop isn’t working in the plugin context is still unanswered. I feel like a solution that uses the have_posts() functions is better for future compatibility and for my personal knowledge, I would like to know the best solution here. Thanks!

Thanks for the idea, but it does not seem to work. I was able to get what I wanted by doing this:

// Print out the select forms
global $wpdb;
$query = "SELECT * FROM $wpdb->posts WHERE post_type = 'post' ORDER BY post_date DESC";
$posts = $wpdb->get_results($query);

if(count($posts) > 0) // equivalent to have_posts()
{
	foreach($posts as $post) // equivalent to while(have_posts())
	{
		echo '<option value="'.$post->ID.'">"'.$post->post_title.'" By: '.get_usermeta($post->post_author, 'last_name').', '.get_usermeta($post->post_author, 'first_name').' - Published: '.substr($post->post_date,0,10).'</option>';
	}
}

I’m still interested to know why the loop wouldn’t work in this context. To my knowledge, the loop isn’t called on this page at all. That’s why I don’t think rewind_posts() helped.

I just had this same problem and found one solution. If you put in the user level number, it seems to interpret as “allow all users with this user level and above to access this menu.” So, for instance, I wanted authors and above to access a menu and I put in:
add_submenu_page('users.php', 'My Plugin Options', 'My Plugin', 2, 'really-cool', 'my_plugin_options');
That seemed to work. I imagine that if you put user level as 0, it should allow everyone to access it. One word of caution is that the documentation does specifically state:

Whilst for legacy reasons, you may also use user level the usage of user level is discouraged for future compatibility and has been deprecated since WordPress 1.5.

So this might not be the best solution.

Yes, that is what I’m trying to accomplish. I am currently doing as you suggested and am posing this question just to see if there is a better way to do it. Thanks for your response!

I’m having the same error. In the codex page for the plugin, there is this bit:

How do I fix the out of memory error?

Scanning your website can take quite a bit of memory. The plugin tries to allocate 128MB but sometimes that’s not enough. You can allocate more by editing wp-config.php and adding the following line before the wp-settings.php require command. This code allocates 256MB of memory. Adjust the “256” figure to suit your needs.

define( 'WP_MEMORY_LIMIT', '256M' );

I tried this and get the same result. I upped the memory to 512 and got a 404 error.

I’m using 2.8.5 btw.

Help please ??

Thanks!

Sorry…I posted in the wrong topic…pleas ignore.

@fishthefly I have been having the same problems that you have and isolated the culprit. When I set up a seller account in the sandbox it gave me an email address in the style of (note…I’ve edited the actual info):

johnso_1238366725_
[email protected]

This is how it appeared in the sandbox listing. In order to get the email address right, I copied and pasted it into the eshop settings. Since the first part of the address and the second part of the address are on separate lines, it actually copied over like this:

tollma_1238366725_ [email protected]

Notice the space between “_” and “p”. This led to the email address being entered incorrectly in the form that submits to PayPal. I imagine you might be having the same problem.