Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Archivist 1.2.4 not working as of MODX 2.5.2 Update #7

Open
sonicpunk opened this issue Nov 18, 2016 · 7 comments
Open

Archivist 1.2.4 not working as of MODX 2.5.2 Update #7

sonicpunk opened this issue Nov 18, 2016 · 7 comments

Comments

@sonicpunk
Copy link

In the frontend the Archivist snippet is not outputting anything and no errors are being written to the MODX error log.

[[Archivist? &target=[[*archivePageID]] &parents=[[*id]],[[*pressespiegelID]] &useFurls=0]]

@ckburnett
Copy link

Looks like the problem may be within the snippet where the sort is set in the query object, here

Commenting out that line brings output back, albeit not sorted.

Replacing that line with the following appears to work in my use case, but it would need more investigation:

$c->sortby($sortBy, $sortDir);

@ksneo
Copy link

ksneo commented Nov 29, 2016

I replaced this by
$c->sortby('FROM_UNIXTIME('.$sortBy.',"%Y")', $sortDir);
$c->sortby('FROM_UNIXTIME('.$sortBy.',"%m")',$sortDir);
$c->sortby('FROM_UNIXTIME('.$sortBy.',"%d")',$sortDir);
and in ArchivistGroupper here

@Lefthandmedia
Copy link

Does the fact that this issue is closed also mean it's fixed?

@rachelmayo
Copy link

rachelmayo commented Feb 7, 2017

I'm having the exact same issue, and after trying both replacements that @ckburnett and @ksneo mentioned (and yes in both php files), my archives are still not appearing. Am I missing something/is there an additional step not mentioned?

[[Archivist? 
&target=`59`
&parents=`53`
&useFurls=`0`
]]

59 = Archives page; 53 = Articles parent page

@Mark-H can you please re-open this?

@jcdm
Copy link

jcdm commented Feb 17, 2017

Hi folks. If I'm reading this correctly, the issue is actually to do with some underlying XPDO functionality which has been reported by @Mark-H and fixed by @opengeek. It's possible the issue was fixed in MODX 2.5.4 - are those still having issues running 2.5.4 and/or above?

@jcdm
Copy link

jcdm commented Feb 17, 2017

@ksneo Solution above worked for me in MODX 2.5.2. Can't vouch for higher than that at the moment. I tried a lot of alternatives but that was the one that output the correct SQL statement for the Y/M/D sort order we're looking for.

@daygon2007
Copy link

Confirmed... @ksneo solution works in ModX 2.5.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants