brettbum

that seems to be it, marking as resolved.

may have answered my own question (will update if I confirm). Think flipping excel got me.

Apparently only a csv from excel saved as a Windows csv file (not msdos csv and not the simple just ‘csv’ option) seems to be pulling in….

Oops gave slightly wrong example

CSV file
Source
/ABA:Aortic_insufficiency_-_medical_management

Target
/aortic_insufficiency_medical_management/

Redirection receives
Source
/cy_medical_management/

Target
/

btw for what its worth, we’re migrating from mediawiki to wordpress hence the _-_ stuff

agree, or paginate the images so that someone could select all the images on a page with multiple pages for the directory, sort of like the post editor.

Just wanted to say thank you for fixing this a few weeks back. ??

not having an issue running this with 4.0 on a studiopress /genesis framework theme for what its worth.

Thanks Carlo!

I too am seeing similar behavior. I have 20.525 images in the index regardless of my attempts to skip folders by year.

I can confirm that I definitely do see the /yyyy/mm/ file structure in wp-content/uploads/

furthermore in my Settings>Media The box for “Organize my uploads into month- and year-based folders” is definitely checked.

For what it is worth, I’m runnng wp 3.9.1 on WPEngine.

Regardless of whether I try to skip or not, I repeatedly get “Step 3/7: indexing image files and backup meta [Fatal Error!]”

Log files

[2.2867] Info: Valid and Invalid meta results written to log
[0.2288] Info: Loaded attachments to memory [26.75 mb]
[0.8297] Info: 13076 Images found [36 mb]
[14.2392] Info: 462 Invalid images found [36.75 mb]
[0.0013] Uknown error: Please see returned value below

Thanks David. I thought I might have known you. I recognized your name, but couldn’t place it in context. ??

will send you a message!

On a separate note, when I went into the Logs tab, I could see that the correct form field information was present, but just not mapped.

In the Logs area, I then mapped the last name to last name, zip to zip, email to email etc.

That solved the problem of the missing Last Name, but I still see the broken code errors.

Note, I think this mapping of form fields would benefit from some documentation. It was not difficult, but would be helpful to know that it needs to be done and where to go to do it and some instructions on how to, or some scenarios or something.

Again, not trying to be critical, just trying to help make this a better experience for others. ??

response from Health Check (running 5.4.29 so that’s not the issue, we are definitely greater than 5.3

Excellent: Your server is running PHP version 5.4.29 and MySQL version 5.5.37 which will be great for WordPress 3.2 onward.

I do not have ajax on in gravity forms. I separately enabled (clicked ‘ON’) Gravity forms no conflict mode which states “Set this to ON to prevent extraneous scripts and styles from being printed on Gravity Forms admin pages, reducing conflicts with other plugins and themes.”

I was still seeing the error, so I also set the Leads plugin option to turn on Compatability Mode in the Global Settings.

Now I get the same error but different lines….

Warning: date_format() expects parameter 1 to be DateTime, boolean given in /public_html/wp-content/plugins/leads/modules/module.metaboxes.wp-lead.php on line 1765

and

Warning: date_format() expects parameter 1 to be DateTime, boolean given in /public_html/wp-content/plugins/leads/modules/module.metaboxes.wp-lead.php on line 1823

While I might try your form editor eventually, my preference would definitely be to continue using Gravity Forms, a plugin that I have grown to trust for myself and my clients for over 3 years.

no worries, although I assume you meant wordpress 3.9.1 not 3.7.1?

I was just giving you a heads up as to the bug. I do not expect you to buy the studiopress theme, although it is one of the most popular themes on the genesis framework this year, yada, yada yada. ( I do not work for them, so it makes no difference to me). ??

Maybe others will experience it or maybe I just ran into a singular bug for the circumstances.

could be that it is missing the Inactive Sidebar (Not Used) groups? (the inactive sidebars from other themes as opposed to the general Inactive Sidebar?

As a workaround, I unchecked the box for the default settings. I copied the CSS first before and then pasted it into the custom css box so that I could benefit from the formatting.

That seemed to solve my problem and prevent the conflict.

Understand. I think the misunderstanding about what overwrites what, plus maybe a little css conflict between the plugin and the theme might have been my problem.