Tux_Rules

And again, post the links to back your statement up:

Thats just not going to happen how many forum posts you open on numerous sites bashing the plugin.

Again, where did I say/demand that you go and manually fix this on my site? Nowhere. No smear campaign, just trying to get an answer as to why it broke.

Please continue with your smear campaign. I have nothing more to say. I prefer to spend time on better things!

Show me the “smear” campaign. All I asked was why it took more than a week to get a response from you on the problem…and it still is not a decent answer.

The strange this is that you dont just need suggestions about fixing the issue from the author but actually wants the author to manually fix the issue on your server.

Nowhere have I stated that I wanted you to manually fix this.
Also, please point out these forum posts threatening you…I really want to see them, so put the links here…
. I think you have no clue as to what happened, and are just trying to make me look bad to cover for you.

As per the user he is posted this question just to make a point even though the issue was easily fixed even before this forum post was opened. Strange!

Um, no, the problem was NOT fixed before posting the question…I waited several days of hearing NOTHING from you before posting the question on my hosting providers forum. The fix was to delete a chunk of code. I wanted to know why the plugin work and, with no other changes/additions/etc. to to blog, it just quit. Worked great for 2 months, then just quit. I am now told it was because of a conflict from another plugin??? Then why did they all play well together for 2 months?

Spreading rumors on forums is not going to help your cause or entitle you to receive personalized free support. I would rather pull the plugin from the repository than fall for such tricks.

What rumors?? I have stated the truth, nothing more, nothing less.
Free support? Really? How about just plain old support for a plugin that seems to have broke things. I’m not the only one to have posted this issue, and I have seen zero help from the author (you) as to how to fix it other than:

Wp-Insert does check if GeoIp class is already defined but still conflicts are occurring mostly from the second plugin which does not check for collisions

which in my case does not apply AS IT ALL WORKED TOGETHER FOR 2 MONTHS!
Then, out of nowhere, poof! It stopped working.
You can continue to try and make it look like I am in the wrong, I don’t care…I just want to know why it broke…something other than:

Wp-Insert does check if GeoIp class is already defined but still conflicts are occurring mostly from the second plugin which does not check for collisions

The above mentioned thread was opened after a long plugin bashing over at the hosts forum (and apparently after fixing the issue!). This really brings your real intentions into question!

My intentions were to show that I did NOT receive an answer from the author (you) as to what could be done to fix it. Fortunately, my hosting provider pointed me in the correct direction and I was able to fix it myself be deleting 3 blocks of code from the plugin.

It is a nice plugin…just no support. And yes, I understand it is free…but me waiting for over a week to get any kind of response from you is just improper…you could have chimed in sooner to give some kind of advice/ask questions to help troubleshoot it.

I am not sure on that…I do know that there had been zero updates on my sites for for at least 2 weeks prior to them crashing…it just came out of the blue….but by removing the code above, it worked again.

I do not believe I am running any other Geo IP enabled plugins…it’s really quite strange that all worked well and then POOF, it breaks…both sites….

The way I fixed it was to take this chunk of code:

function geoip_country_code_by_name_v6($gi, $name) {
  $country_id = geoip_country_id_by_name_v6($gi,$name);
  if ($country_id !== false) {
        return $gi->GEOIP_COUNTRY_CODES[$country_id];
  }
  return false;
}

function geoip_country_code_by_name($gi, $name) {
  $country_id = geoip_country_id_by_name($gi,$name);
  if ($country_id !== false) {
        return $gi->GEOIP_COUNTRY_CODES[$country_id];
  }
  return false;
}

function geoip_country_name_by_name_v6($gi, $name) {
  $country_id = geoip_country_id_by_name_v6($gi,$name);
  if ($country_id !== false) {
        return $gi->GEOIP_COUNTRY_NAMES[$country_id];
  }
  return false;
}

function geoip_country_name_by_name($gi, $name) {
  $country_id = geoip_country_id_by_name($gi,$name);
  if ($country_id !== false) {
        return $gi->GEOIP_COUNTRY_NAMES[$country_id];
  }
  return false;
}

and reduce it to this:

function geoip_country_name_by_name_v6($gi, $name) {
  $country_id = geoip_country_id_by_name_v6($gi,$name);
  if ($country_id !== false) {
        return $gi->GEOIP_COUNTRY_NAMES[$country_id];
  }
  return false;
}

And Arvixe had enabled geoip, so it was not on their end…so, any thoughts on why I had to eliminate that bit of code?

Where did my 2 follow up posts go? The author of the plugin maybe deleted them? How about an answer as to how to fix the geoip error.

This is listed as “resolved”? What is the fix?? I have this issue on 2 sites…how do I fix it?

Fatal error: Cannot redeclare geoip_country_code_by_name() in /home/domain_blocked/public_html/shopping/wp-content/plugins/wp-insert/includes/common/geoip/geoip.inc on line 438

Still doesn’t work.