nightowl99

Forum Replies Created

Viewing 15 replies - 1 through 15 (of 18 total)

  • I would like to do this also, possibly direct to 2 different versions of “thank you” pages, depending on the rating (good or bad).

    • This reply was modified 7 years, 4 months ago by nightowl99.

    I have the same issue. Migrating a site where pages have the .cfm extension results in 404s, even though the slugs are long and descriptive.

    For example, the old URL is
    example.com/news/how-to-redirect-old-permalinks-to-new-site-structure.cfm and the new one is
    example.com/how-to-redirect-old-permalinks-to-new-site-structure/

    The reason for the unfixed 404 given in the log is

    “request for non WP file:.cfm”

    I had high hopes for this plugin since the description says that “It is also useful for migrations that formerly used extensions such as html and shtml, when WordPress does not.”

    Is there any way to include other extensions such as .cfm, or rather, a way to prevent this plugin from rejecting other non-WP extension requests?

    Thank you!

    I have the same problem. No images are showing, only the placeholder.png image, although the posts do have featured images assigned. What could be wrong, any ideas?

    Latest WordPress with Divi theme.

    Forum: Plugins
    In reply to: [Logo Carousel] iOS 8.1.1.

    Just noticed the same issue. Does anyone know how to solve this? It seems that the CSS isn’t loading.

    This is what I get:

    Load from the Instagram feed

P0, UTC:23:29:41.3768, Start plugin.
P1, UTC:23:29:41.3783, Enqueue styles and scripts
P2, UTC:23:29:41.3786, Retrieve Photos
P3, UTC:23:29:41.3789, Check cache
P4, UTC:23:29:41.3829, Using get_transient()...
P5, UTC:23:29:41.3845, No cache found
P6, UTC:23:29:41.3845, Check for access_token
P7, UTC:23:29:41.3847, Try accessing Instagram feed
P8, UTC:23:29:41.3848, Use wp_remote_get() (cURL) to make request
P9, UTC:23:29:50.4697, Request complete
P10, UTC:23:29:50.4698, An error occured.
P11, UTC:23:29:50.4698, Code: 500
P12, UTC:23:29:50.4699, Message: Internal Server Error
P13, UTC:23:29:50.4699, Try request again using Alpine's cURL function
P14, UTC:23:29:59.6023, Request complete
P15, UTC:23:29:59.6024, An error occured.
P16, UTC:23:29:59.6024, Code: 500
P17, UTC:23:29:59.6026, Content Received: <html><body><h1>500 Server Error</h1> An internal server error occured. </body></html>
P18, UTC:23:29:59.6026, Failed using wp_remote_get()
P19, UTC:23:29:59.6026, Check your Instagram feed. If the feed is empty, then the problem is with Instagram. If you see a full page of text, then the problem is with the Alpine plugin or your web server.
P20, UTC:23:29:59.6028, Check Results
P21, UTC:23:29:59.6029, Print Message
P22, UTC:23:29:59.6029, Loading complete
Output

Sorry:

- Instagram feed not found.
Load from cache

P0, UTC:23:29:59.6036, Start plugin.
P1, UTC:23:29:59.6052, Enqueue styles and scripts
P2, UTC:23:29:59.6055, Retrieve Photos
P3, UTC:23:29:59.6059, Check cache
P4, UTC:23:29:59.6060, Using get_transient()...
P5, UTC:23:29:59.6077, No cache found
P6, UTC:23:29:59.6077, Check for access_token
P7, UTC:23:29:59.6079, Try accessing Instagram feed
P8, UTC:23:29:59.6080, Use wp_remote_get() (cURL) to make request
P9, UTC:23:30:8.7053, Request complete
P10, UTC:23:30:8.7054, An error occured.
P11, UTC:23:30:8.7054, Code: 500
P12, UTC:23:30:8.7054, Message: Internal Server Error
P13, UTC:23:30:8.7054, Try request again using Alpine's cURL function
P14, UTC:23:30:17.7950, Request complete
P15, UTC:23:30:17.7950, An error occured.
P16, UTC:23:30:17.7950, Code: 500
P17, UTC:23:30:17.7952, Content Received: <html><body><h1>500 Server Error</h1> An internal server error occured. </body></html>
P18, UTC:23:30:17.7952, Failed using wp_remote_get()
P19, UTC:23:30:17.7952, Check your Instagram feed. If the feed is empty, then the problem is with Instagram. If you see a full page of text, then the problem is with the Alpine plugin or your web server.
P20, UTC:23:30:17.7954, Check Results
P21, UTC:23:30:17.7954, Print Message
P22, UTC:23:30:17.7955, Loading complete
Output

Sorry:

- Instagram feed not found.

    I should probably also mention that this particular page gets hardly more that 10 – 20 hits per day.

    I am having the same problem again. Worked fine for a while and now stopped, but only on my sites which are hosted on Namecheap. This also affects other Instagram plugins. Sites on other hosts are still fine with no problems.

    Hopefully we can find out how to resolve the issue. Thank you, Eric, for hanging in there with us!

    And once again it had stopped with “Sorry: Feed not found” error. After I went to the Tools tab, entered a shortcode to test, same thing happened as before. Load from cache works again, and the feed is showing images on the front once more.

    So, could it be a caching issue? I’m not using any caching plugins.

    Oh no, right now it is working on the front end. Although, on the “Tools” tab I now get errors in both, “Load from IG Feed” and “Load from Cache”. I will keep an eye on it and report if the issue reappears.

    Once again, thank you so much for your hard work! I did send a “cuppa” your way last night… ??

    It’s very well possible that the problem is with the server side of things. However, Namecheap is otherwise a good provider, and they are very willing to help. It’s just that they don’t know what could be missing that would make the plugin work better.

    A search on Google for the direct phrase match of the error output

    “wp-content/plugins/alpine-photo-tile-for-instagram/gears/alpinebot-primary.php(380) : eval()’d code on line 1”

    yields over 6000 results, indicating that this may be a widespread issue that is not limited to my particular install. It’s a shame because I really love this plugin otherwise.

    Thank you,
    Anne

    Sorry to say, this morning the feed was down again. So I had another look at the new Plugin Tools tab, and the System Check says:

    Check: Plugin failed to connect to Instagram.com.
    Code: 500, Message: Internal Server Error.

    Further down in the Plugin Loading Test, I entered the shortcode and got the same errors for the first part (Loading from Instagram Feed), resulting in the “Sorry, Feed not found” output.

    The second part (Load from cache) worked fine and displayed the feed.

    After performing this test the feed displays again on the front end.

    Update: After I saw your last message I did delete/reinstall, and now it works!

    Woo-Hoo! Let’s hope it’ll stick. Thanks so much, Eric!

    Yes, I tried method 2 but was not able to add user either. That’s when I get a 404 page. It’s just strange that it worked fine for a while and then stopped without anyone touching the site. This seems to indicate either a change in the server setup or the Instagram API, no?

    Hi Eric,

    Thanks for responding!

    I tried the update, deleted and reinstalled the plugin, but I can’t even add the user back. After adding the client IDs and authorizing I get “An error occured (No access token found).”

    The “Plugin Tools” tab reveals the following:

    Current PHP version of your server: 5.3.27
    Check: curl_init function found.
    Check: json_decode function found.

    Thank you,
    Anne

    P.S.: Perhaps I should also mention the the callback URI triggers a 404 according to my error logs.
    (/wp-admin/options-general.php?page=alpine-photo-tile-for-instagram-settings&tab=add)

    I spoke too soon. Sometimes it works for a moment, then we get a “Sorry: Instagram feed not found”.

    Hello Eric, I have the exact same problem.

    Have been trying to resolve with the host (Namecheap) but they are not sure what the plugin needs from their end.

    This is what it says in the error logs:

    PHP Parse error: syntax error, unexpected ‘<‘ in /home/xxxxxxxx/public_html/wp-content/plugins/alpine-photo-tile-for-instagram/gears/alpinebot-primary.php(380) : eval()’d code on line 1

    And this is in the “hidden comments”:

    <!-- Failed using wp_remote_get and JSON @ https://api.instagram.com/v1/users/########/media/recent/?access_token=##########################################&count=60 -->

    Can you give us an idea what we’re missing?
    Thank you!

    Edit: I had it set to num=”30″. When I reduced to num=”25″ the feed displayed again.

Viewing 15 replies - 1 through 15 (of 18 total)