alpacaaa/resave_entries

A simple Symphony CMS extension that let you resave your entries after structural section changes.

Resave entries

A simple Symphony CMS extension that let you resave your entries after structural section changes.

• Author: Marco Sampellegrini (alpacaaa)
• Github repository: http://github.com/alpacaaa/resave_entries/
• Release date: 30th March 2012
• Version: 0.2

Installation

Enable the extension as always.

Usage

Go to System -> Preferences and choose the entries of which section you want to resave. As simple as that :)

resave_entries's Issues

No longer working since upgrade to Symphony 2.2.5, just shows "Processing..."

@alpacaaa - Have you used this extension with Symphony 2.2.5? Since I upgraded to the latest Symphony, now when I click on Resave entries, it just says "Processing..." and doesn't do anything.

FYI... I've used this extension successfully with both 2.2.3 and 2.2.4.

Resave Entries deletes out existing Reflection Field values generated by Subsection Manager on Save.

Resave Entries deleting out values Reflection Field values (that are generated from Subsection Manager using the Reflection field's XSLT utility).

When I run Resave Entries, instead of saving the Reflection Field Values, it skips over those values. Or if there is existing Reflection Field values, it empties or removes those values on Save.

To test it wasn't a Reflection field issue, I manually saved a specific entry, and it saves the value as it should.

Do you know what could be causing this?

I have used Resave Entries with a Reflection field in the past with no issue.

I am running Resave Entries, version 0.2, and running Subsection Manager 3.5.1, and Symphony 2.3.3.

Here's my reflection field utility...

<?xml version="1.0" encoding="UTF-8" ?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

   <xsl:template match="data">
      <data>
        <xsl:apply-templates select="entry" mode="search-audio-speaker-reflection"/>
    </data>
   </xsl:template>

   <xsl:template match="entry" mode="search-audio-speaker-reflection">

      <xsl:element name="search-audio-speaker">

        <!-- THIS VALUE IS COMING FROM A SUBSECTION MANAGER FIELD-->

        <xsl:value-of select="concat(speaker/item/first-name/text(),' ',speaker/item/last-name/text())"/>

      </xsl:element>

   </xsl:template>

</xsl:stylesheet>

Process breaks silently if numer of entries per page is too high

I tried to update a large section, including around 1800 entries. Setting the number of entries per page to 50, it broke on the first page. Setting the number to a lower value, it processed some pages, then stopped.

(In the end I managed to update the section using 1 entry per page.)

Is this phenomenon related to memory issues, maybe?

Anyway there should be a warning if the process has not been completed.

Resaving breaks using Symphony 2.5beta2

Using Symphony 2.5beta2, resaving stops with "Processing 1 of NaN" (even if enable_xsrf is set to no in the preferences).

Symphony 2.3 Resave doesn't work

I have section with 20 entries. When I select it and hit the re-save button, Saving 1 of NaN appears and nothing happens. I'm using 0.2, of course.

Process breaks silently if numer of entries per page is too high

Unfortuately this issue still alive. Processing breaks on page 1, and the I get the success message: "Done!"

Ajax request does not exit gracefully on Symphony Error

resave_entries.publish.js

$.ajax still considers Symphony Errors a successful response, so there's no trap for them in the Ajax success callback. Non-destructive but does abort the resave completely with no feedback and leaves the button disabled and logger at "Processing".

Process breaks when number of entries is lower than the one specified

If your section has only 2 entries but you tell the extension to update 50 per page, the counter will run forever, saying "1 of 0", "2 of 0" and so on.