Naz

Hi everyone, while trying to track the reasons for one of my users' frequent logouts, I've found inconsistencies in the session log. It occasionally misses logouts - session timeouts for sure, maybe also changed fingerprints. The log then contains two logins for the same user, with no logout in between. We certainly know this is the case after it happened to my colleague (who can confirm her session timed out without it being logged). We also found the session log is missing completely for the months of April and May. We use the default file-system based sessions and didn't change any logging settings (if they can be changed at all). Our PW version is 3.0. Does anyone have an idea why some session log entries are missing? A complete one is integral to finding the cause of the logouts, as this would enable us to confirm/exclude causes such as a changed session fingerprint.

@Zeka Thanks! For some reason my IDE hadn't downloaded the standalone module files in the modules folder, but only its subfolders. A thorough search for the files you listed led me to the custom module responsible for creating the field data.

I'm working on a page set up by someone else, someone who isn't part of the project anymore. Recently some data inconsistencies have appeared in one field, and I'm trying to find out what causes them. Problem is: I have no idea how the field is populated with data. So maybe some of the clever and helpful people in this forum can give me a pointer where to look. I have a template called "book" whose grandchild is at least one page with the template "date". Each date has a field "start" and a field "end". Several dates can be associated with one book, which is why the template "book" has the fields "earliest date" and "latest date" to identify the whole date range associated with one book. The values of "earliest date" and "latest date" are automatically populated with respectively the earliest "start" and the latest "end" field of all its grandchildren. I tried figuring out where this happens and I have no clue at all. It doesn't happen in the "book" template, nor anywhere in the code (as far as I can see - I looked at all uses of the field names and only saw its value printed out, but not set anywhere). I can't see any setting in the admin that would cause this relationship between the fields. Nor did I find a module that causes it. The FieldType of all fields involved is "integer". Does anyone have an idea where I could start looking?

@adrian Thanks for the welcome and for offering your help! I'm using the latest version of BCE that's available through PW, 1.3.6 (I cannot update the files on the server manually with the latest version from GitHub as there is an issue with the writing rights on the server). I'll message you with example data and all the information that may be relevant for figuring this out.

Hi Adrian, thank you so much for the work you put into this module! It's really making life a lot easier. I've read through this thread and seen that you considered setting the CSV field pairings per template rather than per page. Could you re-consider this option, or point me into the right direction of what I need to tweak to use the module this way? Alternatively it'd already be really helpful if it weren't necessary to add each configurable page separately, but to allow all children, grandchildren etc. of a page to be configurable too. Since that probably helps understanding my issue, here's a little background: I work with a nested page structure in which the parent (A) has a number of children (B) which I'd like to import. Each of these children (B) will have between, on average, one and ten child elements (C), each of which again has at least one child. The current module settings would require me to add each of the children (B) and grandchildren (C) separately to the list of configurable pages in the module settings. Which also means my colleagues - who're not superusers - cannot import anything but the children on the first level (A) on their own, as they have no access to the module configuration and the settings tab, and B and C are only created with the imports. (The easiest solution of course would be to import the pages without field pairings. However, that failed on my local testing environment every way I tried it. Even if the fields were all present in the CSV, and in the same order as in the template settings, the title field never imported correctly.)