|
| nukeNAV |
|
| Search |
|
| Tag This |
|
| Support nukeSEO |
|
|
|
September´s Goal:
|
$100.00
|
| Due Date: |
Sep 30 |
| Gross Amount: |
$0.00 |
| Net Balance: |
$0.00 |
| Left to go: |
$100.00 |
|
| Recent Tutorials |
|
| Feeds |
|
| RavenNuke News |
|
|
|
|
nukeSEO.com FAQ (Frequently Asked Questions)
 Answer | |  What is nukePIE?
nukePIE™ is a replacement for the headlines function in PHP-Nuke's mainfile.php script that is used to display RSS blocks. As a feed reader, nukePIE™ is the opposite of nukeFEED™ which creates feeds from Nuke content. nukePIE™ uses the SimplePie RSS class (included), which supports RSS 2.0 and ATOM 1.0 feeds. It uses BoxOver to optionally display the descriptions for feed items as HTML popups.
[ Back to Top ]
|
| Answer | | How do you use nukePIE?
To use nukePIE™ simply define an RSS or ATOM block in the standard PHP-Nuke blocks administration page. This function has been corrected in RavenNuke™ to correctly update RSS blocks (in many versions of Nuke, the block update function doesn't work under certain conditions).
If you'd like to display full HTML popups using the included BoxOver script (the same script used by nukeSEO Mouse Hover Topic Boxover - and by the administration help function in nukeFEED™), simply add (or change) a line in your config.php (or rnconfig.php for RavenNuke users):
$useBoxoverWithnukePIE = true;
[ Back to Top ]
|
| Answer | | Why must the cache directory be writeable?
The standard PHP-Nuke block RSS reader caches feeds in the nuke_blocks table, along with the definition of the feed. nukePIE uses SimplePie, which caches feeds in files in the cache directory. To do this, the cache directory must be writeable - but it is protected from abuse in a number of ways, including the htaccess file included in the cache directory.
SimplePie automatically refreshes the cache file in the cache directory, but if you delete an RSS block, the unused cache file will remain in the cache directory. You can delete all the cache files (but not .htaccess and index.html) in the cache directory at any time, and any used by active blocks will be restored the next time the block is displayed.
[ Back to Top ]
|
| Answer | | Why is nukePIE better than the standard PHP-Nuke block RSS reader?
nukePIE offers several advantages over the standard PHP-Nuke block RSS reader:
- The ability to read and properly display modern RSS 2.0 and ATOM 1.0 feeds (PHP-Nuke only reads RSS 0.91)
- Significantly improved HTML compliance (e.g. ampersands are no longer displayed in feed item titles)
- The ability to display feed item descriptions either in the link title tags or as full HTML popups via BoxOver, which is optimized for search engines
[ Back to Top ]
|
| Answer | | Why did a feed stop working or breaks my sites validation?
Understand the "garbage in, garbage out" principle: not all feed generators generate valid feeds 100% of the time. Source servers might go down, changes are made - usually these are temporary issues. If there are invalid characters or other HTML issues in the source feed, nukePIE probably won't correct them.
When a feed stops working, there are several things you can do:
- Verify that the feed is displayed correctly using an un-cached reader (e.g. your browser or another feed reader that hasn't previously displayed the feed).
- If the un-cached feed is displayed correctly, clear the cache files (not .htaccess or index.html) in the /cache directory and it should display correctly again. If it still doesn't display correctly, post a message in the nukePIE forum.
- If not:
- Report the problem to the feed generator with as much detail as you are able to determine.
- If the error is displayed in the block, change the block to only be visible to admins until the source is displayed correctly.
- If the error is displayed in page source or in a site message log, change the block permissions or simply ignore it.
[ Back to Top ]
|
|
|
|
|
| Supporters |
|
| User Info |
|
| Recommended Sites |
|
| PHP Magazine |
|
|
|
|
Question
