I was having lots of problems with my converted stuff so I just deleted everything and uninstalled Acidfree entirely. Then I just downloaded the current version again and installed it. I used the Mass Import function to load the first album. Even after telling me that it uploaded the pictures, it said the album was empty. According to Admin>>content, the pictures are there and properly tagged.

Comments

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented

I have gone back and made the albums sticky as recommended (I have no idea why).

When I view Album contents, it shows the albums under it, and even a thumbnail in it. The albums are NOT empty.

vhmauery’s picture

vhmauery commented
Status: Active » Closed (fixed)

I am not sure why making them sticky would change whether or not they appeared. The whole sticky albums thing is so the views query can make sure that the albums are listed first in the photo listing.

If I understand correctly, you are no longer experiencing this bug, so I am going to mark it as closed. In the future, if you report a bug and then later find it is no longer a bug, feel free to close it yourself.

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented
Status: Closed (fixed) » Active

I am still having this problem. My second post was more information.

Even though "Album contents" shows that the album is NOT empty, the album page says "This album is empty." I also get that message immediately following the mass import list saying that pictures had been imported.

vhmauery’s picture

vhmauery commented

Can you check your drupal logs to see if any errors are getting logged?

bkat’s picture

bkat commented

I just updated from HEAD to 5.x-1.x-dev and am experiencing the same problem. When I access any of my existing albums, they are all listed as "This album is empty" with nothing else in the album contents. The album hierarchy in the menu tree is still displaying correctly.

When I installed the new version, I ran the upgrade but it failed because it was trying to create the acidfree_album table that is still there.

vhmauery’s picture

vhmauery commented

Please look in your drupal logs to see if you are getting any error messages.

I have not seen this yet. Until I get some more information than just the symtoms, I cannot fix it.

bkat’s picture

bkat commented

Unfortunately there are no log entries. But I did find out that my problems were related to menus. With the old version I had (and I understand it was and still is a work in progress), I had to manually create the menu entries and use node/$nnn instead of the nice url or else the menus wouldn't expand.

Now with 5.x-1.x-dev, it works correctly when you define the menu entries in the album's edit tab. Thats much better than the work around above so I'm happy now that I've recreated my menu hierarchy.

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented

Okay, I loaded the version labeled "May 1." There were no errors on the install. However, creating an album generates:

user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'DISTINCT(node.nid) AS node_nid FROM node node LEFT JOIN term_node term_node ON ' at line 1 query: SELECT DISTINCT(node.nid), node.sticky AS node_sticky, DISTINCT(node.nid) AS node_nid FROM node node LEFT JOIN term_node term_node ON node.nid = term_node.nid LEFT JOIN term_data term_data ON term_node.tid = term_data.tid AND term_data.vid IN ('14') LEFT JOIN term_node term_node2 ON node.nid = term_node2.nid WHERE (term_node.tid IS NOT NULL) AND (term_data.tid IS NOT NULL) AND (node.status = '1') AND (term_node2.tid = '99') GROUP BY node.nid ORDER BY node_sticky DESC, node_nid DESC LIMIT 0, 15 in C:\www\drupal\includes\database.mysql.inc on line 172.

My recent watchdog entries show:

error php 2007/05/02 - 23:58 You have an error in your SQL syntax; check the ... admin
error php 2007/05/02 - 23:57 You have an error in your SQL syntax; check the ... admin
content 2007/05/02 - 23:57 acidfree: added 2003. admin view
error php 2007/05/02 - 23:57 You have an error in your SQL syntax; check the ... admin
content 2007/05/02 - 23:57 acidfree: added Christmas Parties. admin view
error php 2007/05/02 - 23:56 You have an error in your SQL syntax; check the ... admin

My Apache error logs show:

[Wed May 02 19:58:48 2007] [error] [client 127.0.0.1] ModSecurity: Warning. Match of "rx ^(?:application/x-www-form-urlencoded|multipart/form-data|text/xml)$" against "REQUEST_HEADERS:Content-Type" required. [id "960010"] [msg "Request content encoding is not allowed by policy"] [severity "WARNING"] [hostname "kappabeta"] [uri "/node/add/acidfree/mass"] [unique_id "f80DUcCoAWQAAAooiIsAAAD5"]
'file' is not recognized as an internal or external command, operable program or batch file.
'file' is not recognized as an internal or external command, operable program or batch file.
'file' is not recognized as an internal or external command, operable program or batch file.
'file' is not recognized as an internal or external command, operable program or batch file.
'file' is not recognized as an internal or external command, operable program or batch file.

And after mass importing (http://nanwich.info/acidfree_massimport.jpg) some pictures, it still says the album is empty, but if you go to the Album Contents tab I get this: http://nanwich.info/acidfree_notempty.jpg

vhmauery’s picture

vhmauery commented
Status: Active » Closed (duplicate)

nancyw,

The sql errors you are seeing are Views errors. What version of Views are you using? This problem only shows up when a node_access module (such as private or organic groups) is enabled. Make sure you are using the 5.x-1.6-beta4 or later version. It should be fixed there.

If that is the case, I am closing this as a duplicate. I am not in the mood to find the one that it is a duplicate of, but it is well marked by the DISTINCT error.

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented
Status: Closed (duplicate) » Active

I figured the Sql errors were Views. I believe I am still using 1.5 because -beta4 has too many problems of its own.

However, thet is not the real problem here - the "empty albums" is the real problem. And it has now been opened as another bug report: http://drupal.org/node/141029

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented
Status: Active » Closed (duplicate)

I did update to -beta4 and managed to get its error messages to disappear. That also seemed to solve the "empty album" issue. I'm not happy about going live with a beta Views module.

vhmauery’s picture

vhmauery commented

The sql errors were the real problem. The album empty message was just a symptom. Because the sql query had syntax errors, it returned the null set, the same as if the album was empty.