topquarky

Great. Glad it worked.

Hi Daniel,

Try adding ?forceCheck=foo to the URL on the plugins page (i.e. https://www.domain.com/demo/wp-admin/plugins.php?forceCheck=foo)

If $_REQUEST[‘forceCheck’] is set (to anything), then the plugin checker will check for updates. Otherwise it only checks every 12 hours.

Does that work?

Hi Daniel,

The update script in Version 1.0 is likely still looking on the old domain. If you want it to check the new domain, you’ll need to change the line near the end of your main plugin file:

$__UpdateChecker = new PluginUpdateChecker('https://the_new_domain.com/extend/plugins/my-plugin-slug/update', __FILE__,'my-plugin-slug');

This line gets inserted by Self Hosted Plugins to facilitate the update. It gets inserted when you upload the ZIP, so if you uploaded Version 1.0 to DomainA and Version 1.0.1 to DomainB, then 1.0 checks for updates on DomainA and 1.0.1 checks on DomainB.

Make sense?

Hi.

Can you please send me a copy of the CSV file and actually the view source for the page that triggers the above error. Send to support _@t_ topquark _d0t_ com.

It looks like a jQuery error. That page is AJAX heavy. Did you activate/upgrade any other plugins since the last successful import? There might be a $ conflict going on.

Are you able to provide admin/ftp access to your site for me to get in there need be?

Hi @eduardoborem,

I can’t repeat the issue. I was able to upload a CSV file no problem. I haven’t touched anything to do with the import functionality on any recent updates.

Can you answer me a couple of questions:

1) What browser are you using?
2) Had you done imports successfully before this update?
3) What exactly happens? Do you get the screen with the start button, and then it just doesn’t do anything?

Thanks.
Topquarky

@nzildjian03

Why did you post in this forum? This is for the plugin Self Hosted Plugins. I know nothing about NextGen and cannot help you.

Good luck.

@nzildjian03

Um…

off topic?

Great! Glad we got it working.

Donations are definitely appreciated. You can send to paypal _at_ topquark _dot_ com.

Thanks Josh, and good luck

Cheers
Top Quark

p.s. On my own site, I was able to hook it up so that I’ve can charge for the plugins hosted by self-hosted-plugins and only allow authenticated updates. I’ll get a forum post up on how I did it eventually, but just a teaser to what’s possible.

Hi Josh,

I figured it out. It turns out the readme.txt file led you astray. The bit about disabling the ‘extend/plugins’ feature by adding add_filter('shp_enable_redirect',create_function('$a','return false;')); breaks the whole shebang (told you it was beta).

I removed that add_filter call from your functions.php file and voila, it works now.

I’ll work on fixing the plugin so that filter has the effect it’s supposed to, but in the meantime, leave it enabled and you should be good to go.

Thanks for following through with me until we figured it out.

Cheers
Top Quark

Hi Josh,

Is there any chance you could let me in there to take a look? Let’s get to the bottom of this. WP Admin access would be okay, FTP access would be better (so I can get in there, check error logs, add some debug code, etc).

If you’re obliging, email me credentials to t _at_ topquark _dot_ com

Hi Josh,

I’ve just uploaded version 1.0.8. In that version, I changed the rewrite rules such that the self-hosted-plugins rules come first, thereby taking precedence.

Let me know if that fixed your issue.

Hi Josh,

I don’t think it should be anything to do with the server. Did you try disabling some plugins?

This is a doozy.

Hi @danielverwiej,

Apologies for the delay. I was away for the weekend, out of range.

That’s a strange one. The installation process reads a SQL schema file (pommo/install/sql.schema.php) and processes the commands in there. All of the commands are pretty basic SQL. The above error triggers if and only if the installation fails.

Since you’re on localhost, can you try the following for me. Edit the file pommo/inc/class.common.php. Look for the function “runInstall”. Change line 212 to:

$install = parse_mysql_dump(false); // force error logging

And around line 242 (just before the bmKill() call) add something akin to:

var_dump($logger->getAll());

Please post whatever you find here.

Cheers
Top Quark

Hi Josh,

I had another thought. Try changing the slug of your plugins page to something other than ‘plugins’ (i.e. ‘my-plugins’). Let me know if that does anything.

Hmmm.

Have you tried it in twenty-ten? Or disabling some other plugins?