Forum Replies Created

Viewing 10 replies - 31 through 40 (of 40 total)
  • Thread Starter P3air

    (@p3air)

    Appreciate the offer, but as we said, we’ve de-installed it already. It broke code on several places and we don’t find the concept suitable for our side.

    This is just a recommendation: Tone and attitude of your site and the ‘de-install messages’ may come across a bit – humm – snotty.

    We’ve worked together with many plugin-developer successfully to fix bugs and/or bang out discrepancies. Unfortunately we’ll drop the ball here.

    As your ‘de-install message’ says: Good luck!

    Thread Starter P3air

    (@p3air)

    yes, it sounds dumb.

    We’ve run several WP user-settings and their related GFAG settings. All with the same result: admin has access, subscriber/author is receiving error message

    Thread Starter P3air

    (@p3air)

    all functions can be accessed as an admin, assigning different roles i.e. ‘subscriber’ breaks the functionality. The registered user can can see and access the control-panel. Having assigned the appropriate rights to a ‘subscriber’ it is not possible to i.e. upload pictures or create a category. A ‘blank’ screen is showing with the mentioned error message.
    To our understanding this is caused by insufficient user-rights of a GFA database field.

    Cheers

    Thread Starter P3air

    (@p3air)

    Good news everyone! (Professor Farnsworth)

    It finally works. Michael worked very close with us to get his plugin in our environment running. Excellent work! He went above and beyond himself!!

    This plugin should now work with Atahualpa 3.5.3, especially with custom created widget areas and the plugin “My Customized Widget”.

    This wonderful plugin was worth the fight and some sleepless nights.

    Thread Starter P3air

    (@p3air)

    So here’s where we stand from our site:

    We are running WP 3.0.2 with Atahualpa 3.5.3. We’ve created certain customized widget areas within this theme (Atahualpa 3.5.3 allows you to do so). It seems that his current version 2.02 of mTouch Quiz is now in conflict with these customized widget areas. Atahualpa 3.5.3 is creating a dump file of these widget areas initiating the quiz. The former server error 500 got eliminated.

    Any help is appreciated, it is a great plugin to ‘fight for’

    Cheers

    Thread Starter P3air

    (@p3air)

    Hi Michael,

    thanks for picking the ball. I’ve switched the theme to “twenty ten”. Same error. =(

    But – we are running a mobile switcher theme (Carrington Mobile) – accessing the page the quiz is attempting to load (no 500 error).

    Here is the URL: https://www.P3air/TestQuiz/

    Strange –

    Again, thanks for your help
    Cheerio
    P3air

    Thread Starter P3air

    (@p3air)

    got issue resolved:

    ‘GeoLocation’ doesn’t go well with ‘My Custom Widgets’.

    After installing of ‘GeoLocation’ our SQL database in regards of ‘My Custom Widgets’ got corrupted.

    Disabled ‘GeoLocation’
    Un-installed ‘GeoLocation’
    Disabled ‘My Custom Widgets’
    Dropped SQL database
    Import of backup SQL database
    Enabled ‘My Custom Widgets’
    *LAST custom widget got deleted (was part of the backup, but gets corrupted after restoring)

    we are not sure, if this corruption could be part of some ‘code- residue’ of ‘GeoLocation’ or be tainted ‘My Custom Widgets’ code …

    Luckily we run a backup of our database every night =)

    Advice: RUN a backup of your database BEFORE installing ‘GeoLocation’

    Hope it helps ..

    Cheerio
    P3air team

    we’ve installed it on our site. Let’s just say we are underwhelmed so far.

    We are running WP 3.0.1 and Gigya gave us quite a headache to integrate. We do understand it is a FREE plugin, but Gigya also needs to understand we offer our site as a FREE evaluation platform (so do thousands of others).

    We contacted the ‘support’ only 2 times through their forum. Took 2 days to get back at us with just generic questions. Kinda’ buying time on their site. Reading through the posts we figured it takes +7 days to get to the point from their site.

    The ‘integration’ part of this plugin is awkward, requires your own API setup. Janrain had a better way to deal with that.

    In our view social networking has landed on 5 sites. Unless you run a site with +100.000 hits and user we don’t see a need for 25 different credentials.

    After we migrated our database onto a new server it’s broke. Obviously Gigya socialize plugin doesn’t like to be transferred (Google it up):

    Warning: Missing argument 5 for GigyaSocializeForWordPress::changeAvatarImage() in /home/paircom/public_html/wp-content/plugins/gigya-socialize-for-wordpress/gs-for-wordpress.php on line 182

    First question from Gigya: Did you check your migrated database?
    If you want, you could follow us here.

    Com’on people: If you treat your end-user THAT stupid, what do you expect? Is that the typical developer arrogance? News Flash from us: Get rid of it …

    So, rated 2 stars –

    Cheers
    P3air

    https://www.p3air.com, Sexy BM 3.2.4.2 (beta) – WP 3.0.1

    all the sudden we had the same issue:

    An Error Was Encountered

    The short_link field must contain a valid URL.

    Fix: switched to “tinyurl.com”, save (2x), then back to “b2l.me”, save (2)

    works again

    Hope that works for others too
    cheers

    Stubborn,

    before you slip into suicide mode maybe we can offer some ‘comfort’. It is a very long story but due to the fact we are in aviation we don’t have the pleasure (and luxury) to tell it all. So here in a nutshell: Recently we’ve installed W3-total cache and it messed up bad. And when we say bad, we actually mean catastrophic – We got the 505 internal error, the 404, you name it we got a screen-shot of it. Our bounce-back rate increased to 65%!! Our Apache server was bogging and sputtering. In 76 hours since installment W3 almost crashed our database. We have not contacted the ‘author’ of this product since all and everything is grass-root-development and we are not into blaming games.

    From this point on we are not going to install ANY cache program until it is proven in a test environment. We are not developers and/or code-monkeys (but we learned our lesson).

    Here was our strategy to get out of this flat spin (after a nerve wrecking investigation): we de-activated W3, we deleted (yes, DELETED) .htaccess in your public_html folder to cure the 505 Internal Server Error, gave your server a couple of minutes to recover, logged-in as admin, went into our permalinks and saved our options again (to cure the 404 Not Found Error). Since 48 hours our server runs nice (not perfect) – all links and functions work. Eventually we had to go through all our settings and re-save them. 99% of our options show up the way we had them set up, but we needed to SAVE them AGAIN to re-write .htaccess and all plug-in specific config files.

    We don’t know about any hacking and/or manipulation regarding our database. We definitely know that our trouble was caused by W3 describing behavior you mentioned.

    Hope that helps.

Viewing 10 replies - 31 through 40 (of 40 total)