• Resolved sbuwp

    (@sbuwp)


    I used a CSV file to read in information about the photos. In the process I also set TAG information. Some TAG information I change when creating the CSV file like the TAG NEW to indicate that it is a new photo. With a later CSV generation it is then deleted again. When I search with the photo search for the TAG “NEW”, however, I always see all photos that have had this TAG at some time and not only the photos that currently have the TAG “NEW”. It looks like TAG information is stored permanently.
    Is there a way to delete this obsolete TAG information?

    The page I need help with: [log in to see the link]

Viewing 7 replies - 1 through 7 (of 7 total)
  • Maybe “Table VIII-B14 – Change tag globally” is the answer you’re looking for?

    Plugin Author Jacob N. Breetvelt

    (@opajaap)

    The so called ‘taglist’ needs to be regenerated. Normally this happens automatically, but, because you entered tags ‘through the backdoor’ its not done yet.

    Add any new tag to any photo on the photo admin page, and remove it again. This triggers the remake of the taglist.

    Thread Starter sbuwp

    (@sbuwp)

    Hello Jacob and Serge
    Thanks for the quick reply. I have tried both but it did not help. I think now the TAGs are working properly. I have used setting VIII B14 to rename the TAGs. The old TAG names no longer show up in the TAG list. However, if I then enter the old TAGs in the photo search, the photos that once had the old TAG appear again. Could it be a problem with the photo search function?

    Plugin Author Jacob N. Breetvelt

    (@opajaap)

    Any caching active?

    Thread Starter sbuwp

    (@sbuwp)

    No, I tried it with 2 different browsers (Chrome and Edge).

    Plugin Author Jacob N. Breetvelt

    (@opajaap)

    So you search by search rather than by tags (tagcloud or multitag widget).
    In this case you must tell wppa that the search index must be rebuilt.

    Settings page Table VIII-A8.2

    If its not running yet:
    Preferrably use the Start! button rather than the Start as cronjob button.
    Stay on the page (let the browser tab stay alive) until completion.

    If you use the cronjob button, it may take longer and needs any kind of pageloads so now and then.

    If its already running, be patient. If you keep the setings page open, there will be triggers to re-start the background process every time so it will come to an end in a reasonable time.

    Thread Starter sbuwp

    (@sbuwp)

    Hello Jacob
    Thanks very much for your quick help. Now it runs! It was the Table VIII-A8.2 solution.

    Best regards
    Wolfgang

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘TAG changes don’t work’ is closed to new replies.