---
title: "News Teaser Macro Error After Updating to v3.6.7"
canonical: "https://support.appfire.com/space/SUPPORT/3647963259/News%20Teaser%20Macro%20Error%20After%20Updating%20to%20v3.6.7"
format: markdown
---
This article addresses a display error and rendering timeout issue that occurs after updating the **News Teaser for Confluence** app from version 3.6.6 to 3.6.7 on Confluence Data Center.

## Summary

The update to version 3.6.7 introduces a change where the legacy macro key `newsteaser` is deprecated in favor of `mohami-news-teaser`. Pages containing the old macro key may fail to load, result in a 502 error, or show an "Unknown macro" error if the app is disabled. 

![image-20261014-060954.png](media://ee464b0c-87f9-4d0a-9268-ba804c71524c)

## Scenario 1: Page Fails to Load or Shows 502 Error

After updating to v3.6.7, pages containing the News Teaser macro fail to load, often timing out after 120 seconds or resulting in a 502 Proxy Error. If the app is disabled, the error message `Unknown macro: 'newsteaser'` appears.

### Cause

The affected pages are using the deprecated macro key `newsteaser`. This legacy key maps to the `NewsteaserMacroDeprecated` class, which can cause a `ServiceUnavailableException` and rendering timeouts in newer versions.

### Solution

Update the macro key from the deprecated `newsteaser` to the current `mohami-news-teaser`.

#### Option A: Manual Update via Storage Format

1. Open the affected Confluence page.
2. Access the Page Storage Format (requires Confluence Source Editor or similar administrative access).
3. Search for the string `ac:name="newsteaser"`.
4. Replace it with `ac:name="mohami-news-teaser"`.
5. Save the changes.

#### Option B: Bulk Update via Database

For instances with many affected pages, the macro key can be updated directly in the database.

> **Note:** Always back up your database before performing direct updates. It is recommended to contact Atlassian Support for guidance on bulk macro replacements.

```sql
-- This is to pull all the records with given macro it could be html or html-bobswift

SELECT  distinct s.spaceid,s.spacekey 
FROM CONTENT c
JOIN BODYCONTENT bc
	ON c.contentid = bc.contentid
JOIN SPACES s
	ON c.spaceid = s.spaceid
WHERE 
	c.contenttype IN ('PAGE', 'BLOGPOST', 'COMMENT')
	AND bc.body LIKE '%ac:name="newsteaser"%';



-- Update html with html-bobswift 

UPDATE bodycontent
SET body = replace(body,'ac:name="html"','ac:name="mohami-news-teaser"') 
WHERE bodycontentid in (
  SELECT bc.bodycontentid
  FROM CONTENT c
  JOIN BODYCONTENT bc
      ON c.contentid = bc.contentid
  WHERE c.contenttype IN ('PAGE', 'BLOGPOST', 'COMMENT')
    AND bc.body LIKE '%ac:name="newsteaser"%'
)
;
```

## Scenario 2: Macro Loads but Cannot Be Edited

After manually updating the macro key in the storage format or database, the macro renders correctly in View mode, but the parameters cannot be changed or edited in Edit mode.

This is typically due to Confluence's internal caching (Hibernate/object caches) or local browser cache not reflecting the manual changes made to the storage format.

### Solution

To restore full editability, perform the following steps:

1. **Test on a separate test page:**
  1. Update the macro key for a different test page directly in the database.
  2. Open that page in Edit mode using an Incognito / Private browsing window (or an alternate browser) to bypass local browser cache.
  3. Check if you can edit the existing macro normally.
2. **Account for Confluence caching and indexing:**
  - Since direct database updates bypass Confluence’s internal Hibernate/object caches, changes may not immediately appear in the UI. Please try performing a minor edit and republishing the page, or flushing the Confluence cache.
  - Re-indexing: If the macro still does not reflect the changes, run a Content Indexing pass via Confluence Administration > Content Indexing.

![image-20260909-102010.png](media://997fb78b-61f0-44c9-876f-74928e489a46)