# FIXED - STRING "\_\_\_\_WP\_START\_FOOTER\_\_\_\_" in exported footer.php

**URL:** <https://forum.pinegrow.com/t/fixed-string-wp-start-footer-in-exported-footer-php/8367>\
**Category:** WordPress\
**Tags:** bug\
**Created:** [September 18, 2023, 10:20am UTC](https://forum.pinegrow.com/t/fixed-string-wp-start-footer-in-exported-footer-php/8367 "2023-09-18T10:20:07Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![matjaz](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/matjaz/32/5_2.png) [@matjaz](https://forum.pinegrow.com/u/matjaz)\
**Post date:** [September 19, 2023, 8:48am UTC](https://forum.pinegrow.com/t/fixed-string-wp-start-footer-in-exported-footer-php/8367/4 "2023-09-19T08:48:32Z")

</div>

@MichelyWeb thanks for reporting the issue. The fix is out now, just [released in Pinegrow 7.71](https://docs.pinegrow.com/release_notes/pinegrow-web-editor-7-7/).

A background story:

The Loop and Show Posts actions have the option to show a selected element in case the query doesn’t return any posts.

Up to now, the WordPress actions on such “no posts found” element were not processed. For example Include Template Part action was simply ignored.

In Pinegrow 7.7 we enabled action processing for this element, but a side effect broke the theme export (as you have discovered).

So, in Pinegrow 7.71 this feature was rolled-back and actions are again not processed. But, we do display a warning message and suggesting a workaround of using php code directly on the element (in the source HTML project).

 ![wp](https://canada1.discourse-cdn.com/flex036/uploads/pinegrow/original/2X/6/6a867c2d2a6f06ab0cbbbd646f376edd21ee4d2c.jpeg)

Example of the workaround:

```auto
...
<div class="no-posts">
    <?php get_template_part( 'template-parts/no-results' ); ?>
</div>

```

All the best!

---

_[View the full topic](https://forum.pinegrow.com/t/fixed-string-wp-start-footer-in-exported-footer-php/8367)._