tetontrekker

I had probs with the windows server the very first day and Godaddy let me switch over, but it was within a few days.

WP had been been able to create the folders before that, what changed? With me it was that some time ago GoDaddy moved me to a different server. Either the old absolute path had been auto forwarded then GD turned it off, or WP started processing it different. It was likely GD. It might be worth a peek in your Database, just in case the GD rep was wrong.

I found it in the Database Table: wp_options.

When I Googled the Problem I found that there is/was a place in the WP settings -> media to change the path but I did not have that option on my version, which gave me the clue to look in my DB.

Hopefully either of our issues will help the next person with this prob.

Having same problem (Godaddy server) but only on the primary (first) site of a multisite set up. I was able to upload the jpeg on one of my other sites.

“Unable to create directory uploads/2017/12. Is its parent directory writable by the server?” Even after I created the folder.

FIXED: in the MySQL Database I noticed that the site that did not work had an absolute path to the folder in the options table, the others did not. I changed the broken site upload_path to: wp-content/uploads (removing the absolute path)

• This reply was modified 7 years, 2 months ago by tetontrekker. Reason: I found a fix

Just in case someone finds this in a search; The two warnings about is_archive() and is_home() was caused by YOP Poll. It was also causing an annoying server error, I’ll put in a bug report.

• This reply was modified 8 years ago by tetontrekker.

OK, Thank You!

Update: When I deactivate the PDb plug in the “Notice: is_archive” & “Notice: is_home go away”.

• This reply was modified 8 years ago by tetontrekker.

I hope this helps… I started having the same prob with a custom page outside the loop. Just excel and word docs fail, they worked a month ago or so. I don’t have this plug in loaded, so something else has gone awry. @kirubasankar email me [Moderator Note: Unless you are the developer of this plugin, please keep all support on these forums.] maybe we can compare plug ins and see if we can trouble shoot.

It must be a conflict with another plug in. I’m using Next Gen on 2 other sites, I just did the updates and and it is not getting any errors or warnings.

I’m using it with a custom theme.
https://jhcband.org/photo-albums/

It looks like it happens when the page (or any of the albums) get a hit. I watch who’s on line when I’m working on pages, it looks like it happens when bots hit it too. This is new, it started after one of the recent updates.

My Query Monitor also has a PHP warning on that page:

Warning usort(): Array was modified by the user comparison function 2 wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/nextgen_gallery_display/package.module.nextgen_gallery_display.php:995 usort()
Mixin_Displayed_Gallery_Queries->_entities_to_galleries_and_albums()
ReflectionMethod->invokeArgs()
ExtensibleObject->_exec_cached_method()
ExtensibleObject->__call()
C_Displayed_Gallery->_entities_to_galleries_and_albums()
Mixin_Displayed_Gallery_Queries->_get_album_and_gallery_entities()
ReflectionMethod->invokeArgs()
ExtensibleObject->_exec_cached_method()
ExtensibleObject->__call()
C_Displayed_Gallery->_get_album_and_gallery_entities()
Mixin_Displayed_Gallery_Queries->get_entities()
ReflectionMethod->invokeArgs()
ExtensibleObject->_exec_cached_method()
ExtensibleObject->__call()
C_Displayed_Gallery->get_entities()
Mixin_Displayed_Gallery_Queries->get_included_entities()
ReflectionMethod->invokeArgs()
ExtensibleObject->_exec_cached_method()
ExtensibleObject->__call()
C_Displayed_Gallery->get_included_entities()
A_NextGen_Basic_Album_Controller->index_action()
ReflectionMethod->invokeArgs()
ExtensibleObject->_exec_cached_method()
ExtensibleObject->__call()
C_Display_Type_Controller->index_action()
Mixin_Displayed_Gallery_Renderer->render()
ReflectionMethod->invokeArgs()
ExtensibleObject->_exec_cached_method()
ExtensibleObject->__call()
ExtensibleObject->call_method()
Mixin->call_parent()
A_NextGen_Basic_Album_Routes->render()
ReflectionMethod->invokeArgs()
ExtensibleObject->_exec_cached_method()
ExtensibleObject->__call()
C_Displayed_Gallery_Renderer->render()
Mixin_Displayed_Gallery_Renderer->display_images()
ReflectionMethod->invokeArgs()
ExtensibleObject->_exec_cached_method()
ExtensibleObject->__call()
C_Displayed_Gallery_Renderer->display_images()
M_NextGen_Basic_Album->ngglegacy_shortcode()
C_NextGen_Shortcode_Manager->callback_wrapper()
C_NextGen_Shortcode_Manager->__call()
C_NextGen_Shortcode_Manager->album__callback()
do_shortcode_tag()
preg_replace_callback()
do_shortcode() Plugin: nextgen-gallery

I hope this helps,
Julie

Thank you for the fast reply. I had a little more time to look at it. I looked in my error log, there were some mistakes in my code but didn’t see anything that would effect this.

I also found I was having this problem within my theme. Everywhere I have an image with a simple link, I was getting a wheel and the link will not work. When I deactivate nextgen the links work properly.

https://jhcband.org/another-way-to-support-the-jhcb/
This page is within my theme. The donate button in the widget is actually a form, not an image link so it worked. The “Get Started” link in the post, the twitter link, and the facebbok link in the foot section all gave me the wheel.

I tracked it down to the FancyBox – jQuery Plugin. In the nextgen settings I changed “What effect would you like to use? to “none” and it fixed my problem.

I hope this benefits anyone else that is having this problem.
Thank Again,
Julie
(I’m trying to spam, it’s just that this page had some good examples of the problem I was having)

did you find an answer? I’m trying to do the same.

Never mind, I see on another post PHP 5.4 is a requirement. I will install and try again.

I got it working, I took out get_currentuserinfo(); and it worked.

I figured it out, thank you

OOPs, I used the $boardfirst in my message output.

This seems to have been fixed.