MintJoomlaMintJoomla

Import - modified date is set to current date - Missing feature or bug?

Problem Problem | Reviewed Reviewed | Cobalt 8 | Hits: 1609 | Comments: 33 | Bookmarked: 1 | Followers: 6

pepperstreet VIP
Total posts: 3,837
09 Jan 2016 13:25

Hello, I am importing older ME-Resources records (.CSV file).
The records‘ modified date (mtime) is always set to the current import date. Why is this!?
I would like to keep the original records infos as they are. How to keep mtime?
Would be useful to have it in fields assignment, too. Currently there is only ctime. :(

Related Idea / Request

In general, it would be nice to see and assign all core fields
i.e. all dates, hits, votes, metadata, alias, author etc.

Last Modified: 26 Mar 2017

Quote

Sergey
Total posts: 13,748
26 May 2016 16:02

I am sorry, I am in Moscow now. Limited access to the source code. I do not have my Mac with me. So no development environment. I'll create a build as soon as I get home.

Quote

pepperstreet VIP
Total posts: 3,837
26 May 2016 23:51

Sergey I am sorry, I am in Moscow now. Limited access to the source code. I do not have my Mac with me. So no development environment. I'll create a build as soon as I get home.

NP! Enjoy your trip to Moscow and the JoomlaDay. Would be nice to see some impressions i.e. kinda diary, selfies, pictures, videos. Have fun!

Quote

pepperstreet VIP
Total posts: 3,837
28 Jun 2016 17:46

Sergey I added modification time.

Cobalt 8.707 seem to have issues. Also dates are not set correctly. See screenshots:

Field assignment works fine:
field_assignment_csv_to_core_dates

CSV contains date/time in default format YYYY-MM-DD 00:00:00
csv_original_ctime_mtime

Cobalt result after import: mtime is set to current import time :(
cobalt_mtime_equal_importtime

Second try on next day for proof:
cobalt_mtime_equal_importtime_2nd_try

Quote

Sergey
Total posts: 13,748
29 Jun 2016 05:10

Thank you for report. I was trying to install php7 on my mac and completely messed up. Nnow apache does not work. FOr few days already I cannot make it work again. Looks like I'll have to start from scratch and reinstall OS.

As soon as have my IDE running I'll check that out.

Quote

Sackgesicht VIP
Total posts: 1,636
29 Jun 2016 06:57

use the

brew install php70

brew install php56

to change from php56 to php70

brew unlink php56

brew link php70

check the apache config (adjust the path)

2016-06-29_15-00-47

add specific php7.conf

2016-06-29_15-01-45

Quote

Sergey
Total posts: 13,748
30 Jun 2016 04:54

That all was done but Apache always complained that it cannot load php7_module.

Thsi is what I have

https://github.com/Homebrew/homebrew-php/issues/3073

Quote

Sackgesicht VIP
Total posts: 1,636
30 Jun 2016 05:14

make sure that ALL php 5 module directives in apache configuration are commented out, even if they come after the php 7 line.

I remember, that i had some small issues when under php7 still php5 module directives were active

Quote

pepperstreet VIP
Total posts: 3,837
01 Jul 2016 07:51

pepperstreet

Sergey I added modification time.

Cobalt 8.707 seem to have issues. Also dates are not set correctly. See screenshots:

FYI, no difference in Cobalt 8.715

cob_8715_import_mtime

Quote

Sergey
Total posts: 13,748
05 Jul 2016 05:44

That turned out that I cannot change modification time. There is special mechanism that ensures to alter that date on every record save.

Quote

Sackgesicht VIP
Total posts: 1,636
05 Jul 2016 10:12

Sergey That turned out that I cannot change modification time. There is special mechanism that ensures to alter that date on every record save.

Which for me is correct ...

A solution could be:

1) import modification date into other field

2) use a sql query to update modified date with the imported field

3) optional - remove imported field

Quote

pepperstreet VIP
Total posts: 3,837
05 Jul 2016 13:03

Sergey That turned out that I cannot change modification time. There is special mechanism that ensures to alter that date on every record save.

Bummer. Too bad :(

Sackgesicht Which for me is correct ...

I don't think so. Why can't I override when I assigned it during import. Can't we check for this assignment? If assigned, then override it...

Why and where is it used? It's always the Import-time, no matter if I UPDATE or create NEW records. So, for what purpose is it important?

BTW, there is also INITIAL-date, which seems to store the same import date.

Quote

pepperstreet VIP
Total posts: 3,837
05 Jul 2016 13:11

Sackgesicht A solution could be: 1) import modification date into other field 2) use a sql query to update modified date with the imported field 3) optional - remove imported field

Thanks for the tip, but I am not convinced. Too much hassle for a missing core feature.

As you may remember: Too much "Gefrickel". Not frickel-free :) ;)

Powered by Cobalt

Login (copy)