Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author WPTrashPanda

    (@jprescher)

    So what you need is an App ID and App Secret so Facebook can generate an access token to give you access to the events data.

    1. Visit Facebook Developers
    2. Under “My Apps” Add a New App by choosing Website App
    3. From there just follow the screens until you obtain your App ID and App Secret.
    4. Don’t forget to make your app active and ready for use under Status and Review.

    Thread Starter birdpuk

    (@birdpuk)

    https://www.icloud.com/photostream/#A1GgZLKuJIk6XM

    There seems to be an issue with your settings page(see above link). Have gotten the same results with several different WordPress configurations. By replacing the garbage with the values in the two fields instead of adding to the end, I was able to get the ap did and secret to take and actually imported some events.

    Am concerned however because of the page and some other problems that popped up when try to install with the customizr theme. Hopefully I can activate the pro now and give the rest a good test. Would not let me activate pro without setting the fac book app in the standard pluggin first.

    Thanks.

    Thread Starter birdpuk

    (@birdpuk)

    now when i try to activate pro i am getting a different error

    Plugin could not be activated because it triggered a fatal error.
    Parse error: syntax error, unexpected ‘}’ in /srv/dougknowles/wp-content/plugins/facebook-events-importer-pro/facebook_events_pro.php on line 117

    Plugin Author WPTrashPanda

    (@jprescher)

    The function near line 117 just removes the notice to upgrade. From your screen shot it looks like a key function is failing to initiate. lol, “the garbage” is where the values should obviously be so clearly there is an error with your install or a conflict preventing WFBE from working. I just sent you new copies of both files to test if it was an error with the downloads. My hunch is that the Smash Balloon Custom Facebook Feed could be conflicting. Try deactivating that and see if the error is removed. Thanks for not giving up and purchasing the Pro version. You have my email for support or continue to post here.

    Thread Starter birdpuk

    (@birdpuk)

    not activated and happens without it installed

    Thread Starter birdpuk

    (@birdpuk)

    removed it completely am still getting this message when activating yours

    The plugin generated 596 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.

    Thread Starter birdpuk

    (@birdpuk)

    i have now just installed your plugin on a fresh unaltered install of WordPress and I am getting all the same errors.

    I have added the screens to the link above

    Plugin Author WPTrashPanda

    (@jprescher)

    The issue was the use of the shorthand PHP open tag vs the long.

    <? //shorthand
    ?> 
    
    <?php //longhand
    ?>

    Once this change was mad in 2.3.3 the errors disappeared. Thanks for the help in solving this.

    Thread Starter birdpuk

    (@birdpuk)

    for the record, I am running on NGINX installed using Ajenti V control panel instead of Apache. For some reason default value of on for short_open_tag is turned off. i have also commented in the Ajenti V knowledge base area for running wordpress on how to fix it when setting up in that environment

    https://stackoverflow.com/questions/2185320/how-to-enable-php-short-tags/a&gt;

    This can be done by enabling short_open_tag in php.ini:

    short_open_tag = on
    If you don’t have access to the php.ini you can try to enable them trough the .htaccess file but it’s possible the hosting company disabled this if you are on shared hosting:

    php_value short_open_tag 1
    For the people thinking that short_open_tags are bad practice as of php 5.4 the <?= … ?> shorttag will supported everywhere, regardless of the settings so there is no reason not to use them if you can control the settings on the server. Also said in this link: short_open_tag

    Plugin Author WPTrashPanda

    (@jprescher)

    Good tip birdpuk. Shorthand is a bad habit and really shouldn’t be used in plugin development. I wouldn’t expect anyone to have to alter their php.ini to run this plugin so I just switched all the tags in the latest release.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Facebook app building/connecting.’ is closed to new replies.