usdy

PHP configuration is being done via a web interface setup page provided by my host. The configuration panel lools like this.

So there’s no php.ini in my root dir. Creating one doesn’t affect the ‘Forbidden’ behavior.

Maybe on the screenshot you find some setting to change?

I’m wondering there is no debug messages or so to investigate in… Any idea?

@ acub: Thanks for the line. Your solution to add header.archive-header {display: none;} to the CSS is slim and easy to add/remove.

I’m adressing the same issue and am happy to see an active dev Sayontan Sinha supporting the community. Great job so far, photonic is a fantastic enrichment!

Regarding the limitation of flickr, I’d recommend to have a “see more” button or something like this (similar to the setting you have foreseen under “Generic Options – Layout – Archive View Thumbnails”). Or maybe a way better enhancement: You know how many photos one set contains (flickr tells you). I.e. a set contains 250 photos and your per_page setting in Photonic_Flickr_Processor.php is set to 100, are you able to perform three pulls to fetch all the images?

Somehow, I do agree with that. Until then, I’m happy to provide you with any debug info when needed.

Never heard about SuHosin. Whatever it is, is there a way to find that out and verify if that causes my issues?

Regarding your questions:
1. My host tells me they are using CentOS (V4.2) + BlueQuartz (V4.8) as management interface. Services as Apache, MySQL, PHP, Mail, FTP, SSH are preinstalled (see that).
2. My web host is called world4you, which you’ll find here.
3. No WP multisite function in use
4. The WP site is in a subdirectory. The root contains a .htaccess file with the following content:

# W4Y Redirect
RewriteEngine on
RewriteRule ^(/)?$ https://reise.dextroid.at [R=301,L]

The folder containing the WP Inject test installation does not contain any other htaccess file.
5. WP version is 3.9.1
6. Tried with Firefox and IE

Disabling the htaccess file doesn’t change the situation.

So well, that’s really a pitty, the plugin seems so be great work. Hope we can figure out where’s the bug.

@ leehodson: At least in the wp-content/uploads folder, there are no images being dropped by WP inject. So I have no possibility to compare persmissions against other uploaded images.

Saving and reopening the post in the backend editor doesn’t change the situation, unfortunately.

Regarding your question about any other plugins, I’ve created a brandnew WP installation with only stock settings and all the actual versions. No change… ??

@ Thomas Hoefter: Interesting question and yes, I am able to set a featured image using the regular procedure. After doing that, WP creates folders inside the wp-content/uploads folder (2014 rwxr-xr-x / 05 rwxr-xr-x) and there I find the uploaded original image and the processed images with different resolutions. Files have rw-r–r– permission.

@ leehodson: The error log unfortunately doesn’t show a new entry after receiving the message “Forbidden”.

@ Thomas Hoefter: I followed the link you’ve attached and found out that your plugin saves all images in the uploads folder under wp-content. I’ve checked permission to that directory (and also the subs) and found out that all permissions are set to 755. As far as I could find out, that should be good, right?

Got new info. I’ve generared the error logs and I find following line:

[Sun May 25 00:02:46 2014] [error] [client 188.45.37.47] Script timed out before returning headers: options-general.php, referer: https://www.dextroid.at/wordpress/wp-admin/options-general.php?page=flickrps.php

Hope that helps.

esmi, I’m not sure I understand the motivation of your message. The issue seems not to be resolved, rather people still report the issue as mentioned at the very beginning. But maybe I do misunderstand the purpose of your post? I apologize, if so.

To support the developer miro.mannino with further information (and at the bottom line to stick on the main issue), I’ve tried to de- and reactivate the plugin and use my year 2010 API key, without success. After saving the config, after a while I still receive the 500 internal server error message.

Sure! ?? Well, the whole message is really just: Forbidden. See that screenshot

When I disable the “Save Images to Server” option, inserting an image to the post WORKS!

But when I try to use a selected image as featured image (which is my main purpose to use your plugin), I still do get the “Forbidden” message.

Looks like some kinda rights issue, what do you think?

Using a newly generated API key (May 14). After clicking ‘save changes’, I receive a 500 server error after app. 2 min timed out. Same for the October 2010 API key.

Flickr photostream was newly installed in version 3.1.

Is there any debug?

Firsh, first thanks for taking care.

Fortunately, I’ve created another API key in 2010. Unfortunately, also that key reports invalidity.

I’ve then tried to add your code underneath the four mentioned lines and added “https” to lines 29-31. After entering my 2010 API key, I receive “There was some problem figuring out your endpoint”.

So I uncommented lines 211-213 but now after pushing “save changes” the page loads indefinitely and ends up with a 500 internal server error message.

1. done a plugin uninstallation first to have a clean config page.
2. reinstalled Flickr Photostream 3.0.1, activated it.
3. modified phpFlickr.php via FTP using notepad++, lines 29-31/211. reup.
4. back in wp-admin, settings > flickr photostream.
5. 2nd tab, got a new api key
6. paste api key and user id in settings dialogue, save changes.
7. page’s loading. and loading. and loading.
8. blank page as result. re-entering settings, all fields are blank.

Guess that’s a dead end, right? ??

By the way, where’s the dev??

stefanozanardipv, what’s the point? I’m running an web-based editor. I’m not sure, do you think it makes any difference?

When I modify the settings in lines 29-31 / 211 and hit “Save changes” in the plugin settings, the page reload ends up in a timeout. Changes are not being saved. When I reenter the settings dialogue, there’s still the old ID entered. So even requesting a new code won’t help here.