shamus

Upon a re-import of data (generated originally from BCE's export as csv feature), BCE appears to be treating the related field as type TINYTEXT (limiting to 255 characters), even though the field is defined as type MEDIUMTEXT (collation: utf8_general_ci). I've tested this a number of times. Full paragraphs (i.e. greater than 1000 characters) that I copy into the field's textbox (using page edit) and then save, end up being cut off to 255 characters over and over upon a re-import of data. Checked CSV and it contains the full paragraph. Any idea as to why the predefined type is changing upon CSV import?

Note: ATTACHING A FOLLOWUP to this post from earlier...i.e. when I try to import just 3 fields, 1 being a multi-value page fieldtype, I get the following error: ProcessWire: ProcessPageEdit: Page 30 is not valid for product_item_weight_or_count (Page 30 does not have required parent 1055) So the question becomes, how do I properly re-import this data? The exported data shows piped values correctly: e.g. 30|50|75 How should the import data appear and include the required parent reference? Also, how do I define the CSV Field pairings? e.g. parent.subfield OR simply the template fieldname (product_item_weight_or_count)

Hello, I'm having issues w/ BCE importing a CSV that is first generated by the BCE CSV Export feature. For some reason, when I re-import, I'm getting the following error: "Session: The number of columns/fields in your CSV is not enough for number of fields defined for this import. Nothing can be safely imported." I've double checked the CSV's column names to ensure that the number of fields match the related template. I've also then inputted the "CSV Field Pairings" exactly to match the template and the CSV. I've tried this with "ignore first row" unchecked w/ a corresponding CSV that includes the fieldnames in the first row, and also tried checking the "ignore first row" option and excluding the corresponding first row in the CSV. I have a total of 45 fields in the template, 45 defined in the CSV Field pairing setting box, and 45 columns in the CSV. Not sure what I'm missing here, but could this have anything to do w/ the fact that I'm using page fieldtypes for at least 5 of the fields / columns? Other than that, I can't make heads or tails as to where the error lies.

I have already replied to a related post by Joss (https://processwire.com/talk/topic/8672-forged-again/) but I just came across this topic and seems there's been a lot more discussion here regarding this "forged request" issue. Anyways, I'm running PW 2.5.3 and am experiencing the dreaded "TemplateFile: This request was aborted because it appears to be forged." error described herein while trying to log into the admin interface AND using a mobile device running iOS. I have tested the admin login successfully using droid mobile devices (both phone and tablets) , along w/ most desktop browsers including IE8-11, FF29+, and most recent Opera and Safari versions. Curious if anyone has experienced the same thing w/ iOS 7 and has a recommended fix? Note: since find this post, I have tried using Nico's tips in his troubleshooting guide regarding altering CSRF config settings (e.g. $config->protectCSRF = false;$config->sessionChallenge = false; $config->sessionFingerprint = false;). After integrating these changes, this resulted in my login request being bounced back to admin login form, without any error (and failed login). ------------ PLEASE IGNORE: FIXED ---------------------------------- Cookies must be enabled...had wrong settings.

I'm running PW 2.5.3 and am experiencing the dreaded "TemplateFile: This request was aborted because it appears to be forged." error described herein while trying to log into the admin interface AND using a mobile device running iOS. I have tested the admin login successfully using droid mobile devices (both phone and tablets) , along w/ most desktop browsers including IE8-11, FF29+, and most recent Opera and Safari versions. Curious if anyone has experienced the same thing w/ iOS 7 and has a recommended fix? ------------ PLEASE IGNORE: FIXED ---------------------------------- Cookies must be enabled...had wrong settings.