[Valid RSS] This is a valid RSS feed.


This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.


  1. <?xml version="1.0" encoding="utf-8"?>
  2. <!-- generator="FeedCreator 1.8.0-nukeFEED (" -->
  3. <rss version="2.0">
  4.    <channel>
  5.        <title>Ravens PHP Scripts And Web Hosting News - Ravens PHP Scripts</title>
  6.        <description></description>
  7.        <link></link>
  8.        <lastBuildDate>Wed, 20 Sep 2017 05:30:35 -0500</lastBuildDate>
  9.        <generator>FeedCreator 1.8.0-nukeFEED (</generator>
  10.        <item>
  11.            <title>Raven Is Back At Least For A While!</title>
  12.            <link></link>
  13.            <description><![CDATA[<p><span title="Raven Is Back At Least For A While!">Greetings to all! &nbsp;My health is doing better and I'm trying to get back in some kind of regular routine. I feel like I'm having to learn to walk all over again, but things are starting to fall into place, somewhat, LOL! &nbsp;I have missed many of you and hope to catch up the best I can. Please let me hear from those of you that are still using RavenNuke (tm) to show you still want development. &nbsp;I will basically support v2.51 the best I can while Neralex will be leading the charge in RavenCMS, at least that's the plan for now. I will open up a <a href=""><strong>Forum topic</strong></a> also for your responses.</span></p>]]></description>
  14.            <author> [email protected] (Raven)</author>
  15.            <guid isPermaLink="false"></guid>
  16.        </item>
  17.        <item>
  18.            <title>Some GitHub downloads were blocked for safe browsing</title>
  19.            <link></link>
  20.            <description><![CDATA[<p><a>Bleeping Computer</a> reports that executable files (.exe, .msi, etc.) were showing safe browsing errors in Google Chrome and Firefox for around 8 hours yesterday (25 January, 2017).</p>
  21. <p>Although this only affected a small number of users, it would be pretty significant for the commercial and open source projects hosted there who use executable downloads.</p>
  22. <p>Neither the Bleeping Computer article nor the <a href="">GitHub blog</a> explains what happened or how it was fixed.  Since this had to be caused by something GitHub changed (and subsequently fixed) without requiring changes to the browser, explaining what happened would be helpful not only to impacted projects to assess how they handle downloads and their GitHub accounts in the future, but also others who might avoid similar issues.  It would also help those considering hosting projects on GitHub decide how to proceed.</p>
  23. <p>What do you think? &nbsp;Comment <a href="">here</a>.</p>
  24. <p style="text-align: center"><img src="" alt="GitHub Safe Browsing Warning" width="600" height="309" /></p>]]></description>
  25.            <author> [email protected] (kguske)</author>
  26.            <guid isPermaLink="false"></guid>
  27.        </item>
  28.        <item>
  29.            <title>PMC Theming System (PMCTS) for RN</title>
  30.            <link></link>
  31.            <description><![CDATA[<p>&nbsp;</p>
  32. <div>&nbsp;</div>
  33. <div>The increasing number of new registrations from temporary email accounts and free email accounts caused me to delete all of the accounts on my site and also close my site to new registrations. &nbsp;Although my site is basically used for working on my new theming system, it would be nice to have those new features that you are describing in your post. &nbsp;All of the RN sites that I visit have been closed down because let's face it, Nuke, in general, has died on the vine. &nbsp;But, if RN could get added to the large list of software in Softaculous it might help bring it back. &nbsp;I noticed PHP-Nuke is added. &nbsp;</div>
  34. <div>&nbsp;</div>
  35. <div>&nbsp;</div>]]></description>
  36.            <author> [email protected] (kguske)</author>
  37.            <guid isPermaLink="false"></guid>
  38.        </item>
  39.        <item>
  40.            <title>Part-time, project-based PHP work</title>
  41.            <link></link>
  42.            <description><![CDATA[<p>&nbsp;Please PM kguske if you're interested in part-time, project-based PHP work.</p>]]></description>
  43.            <author> [email protected] (kguske)</author>
  44.            <guid isPermaLink="false"></guid>
  45.        </item>
  46.        <item>
  47.            <title>RNYA and nukeSPAM enhancements</title>
  48.            <link></link>
  49.            <description><![CDATA[<p><span>It's been a while, but we haven't stopped looking for ways to help websites expand their reach and operate more efficiently. &nbsp;Since member management continues to be a challenge, especially with the continued onslaught of spammers, the current focus for nukeSEO is on these areas.</span></p>
  50. <p>Your feedback in the forums will help determine priorities. &nbsp;Please add comments&nbsp;<a href="">here</a>, where you'll also find more detailed discussion on these topics.</p>
  51. <p>Currently, we're looking to:</p>
  52. <ul>
  53.    <li>RNYA&nbsp;
  54.    <ul>
  55.        <li>Replace the grid, search and maintenance functions with the DataTables class used in nukeSPAM</li>
  56.        <li>Add functions to delete users without notification and add domain / subdomain to the blocked mail domains list</li>
  57.        <li>Share blocked mail domains list across sites</li>
  58.        <li>Add tools for removing members who never logged in, identifying members from blocked domains</li>
  59.    </ul>
  60.    </li>
  61.    <li>nukeSPAM
  62.    <ul>
  63.        <li>Integrate nukeSPAM with RNYA&nbsp;for simplified domain blocking (e.g. add this domain / subdomain to the blocked domains list)</li>
  64.        <li>Integrate nukeSPAM with additional blocking tools for:
  65.        <ul>
  66.            <li>Email validation services</li>
  67.            <li>Disposable Email Address lists / services</li>
  68.        </ul>
  69.        </li>
  70.        <li>Auto-block domains / subdomains with multiple offenders</li>
  71.    </ul>
  72.    </li>
  73. </ul>
  74. <p>Please let us know what you think at&nbsp;<a href=""></a>.</p>]]></description>
  75.            <author> [email protected] (kguske)</author>
  76.            <guid isPermaLink="false"></guid>
  77.        </item>
  78.        <item>
  79.            <title>PHP Resources</title>
  80.            <link></link>
  81.            <description><![CDATA[<p>In addition to providing reviews of web hosting companies, provides a <a href="" target="_blank">collection of PHP resources</a>, including:</p>
  82. <ul>
  83.    <li>Tutorials for PHP beginners</li>
  84.    <li>Intermediate and Advanced PHP Tutorials</li>
  85.    <li>PHP Reference Material</li>
  86.    <li>PHP Development Tools</li>
  87.    <li>PHP&nbsp;Frameworks</li>
  88.    <li>and more</li>
  89. </ul>
  90. <p>Check it out!</p>]]></description>
  91.            <author> [email protected] (kguske)</author>
  92.            <guid isPermaLink="false"></guid>
  93.        </item>
  94.        <item>
  95.            <title>Modern PHP server stack</title>
  96.            <link></link>
  97.            <description><![CDATA[<p>&nbsp;Carl Alexander describes the <a href="" target="_blank">modern PHP&nbsp;application server stack</a> with recommendations for:</p>
  98. <ul>
  99.    <li>Web server</li>
  100.    <li>HTTP&nbsp;Cache</li>
  101.    <li>PHP</li>
  102.    <li>Database Server</li>
  103.    <li>Object Cache</li>
  104.    <li>Deployment Tools</li>
  105. </ul>
  106. <p>This is a well-written article based on a presentation from WordCamp San Diego 2016, later republished in Smashing Magazine.&nbsp; Check it out!</p>
  107. <p><img width="700" height="92" src="" alt="" />&nbsp;</p>]]></description>
  108.            <author> [email protected] (kguske)</author>
  109.            <guid isPermaLink="false"></guid>
  110.        </item>
  111.        <item>
  112.            <title>Favicon &amp; App Icon Generator</title>
  113.            <link></link>
  114.            <description><![CDATA[<p>What are Favicons? <br />
  115. <br />
  116. Favicons are small 16x16 icon files that are displayed next to the URL of your site in a browser's address bar. Additionally they're often displayed next to the name of your site in a user's list of open tabs and bookmark listings making it easier for the user to quickly identify amongst other sites. <br />
  117. <br />
  118. What are App Icons? <br />
  119. <br />
  120. App Icons are the images you press on your smartphone to launch an application. As newer phones are released with higher resolution screens, higher resolution app icons are needed. Developers still want to maintain support for the older phones with lower resoltion so when you create an app icon you need to create several size variations of the same image. This is true for all smartphones like the iPhone and Android, and even tablets like iPad. <br />
  121. <br />
  122. more: <a title="Favicon &amp; App Icon Generator" href="">Dan's Tools</a></p>]]></description>
  123.            <author> [email protected] (kguske)</author>
  124.            <guid isPermaLink="false"></guid>
  125.        </item>
  126.        <item>
  127.            <title>Apache HTTP Server Tutorial</title>
  128.            <link></link>
  129.            <description><![CDATA[<p>Apache HTTP Server Tutorial: .htaccess files <br />
  130. <br />
  131. What they are/How to use them <br />
  132. <br />
  133. .htaccess files provide a way to make configuration changes on a per-directory basis. <br />
  134. <br />
  135. .htaccess files (or &quot;distributed configuration files&quot;) provide a way to make configuration changes on a per-directory basis. A file, containing one or more configuration directives, is placed in a particular document directory, and the directives apply to that directory, and all subdirectories thereof. <br />
  136. <br />
  137. Note: <br />
  138. <br />
  139. If you want to call your .htaccess file something else, you can change the name of the file using the AccessFileName directive. For example, if you would rather call the file .config then you can put the following in your server configuration file: <br />
  140. <br />
  141. AccessFileName &quot;.config&quot; <br />
  142. <br />
  143. more: <a title="Apache HTTP Server Tutorial" href="">Apache</a></p>]]></description>
  144.            <author> [email protected] (kguske)</author>
  145.            <guid isPermaLink="false"></guid>
  146.        </item>
  147.        <item>
  148.            <title>RavenNuke Fork</title>
  149.            <link></link>
  150.            <description><![CDATA[<p>&nbsp;I wrote at an earlier time about forking RavenNuke but have now decided not to. The reason is simple, there is nothing that can be forked. It's such a complete system I find nothing to improve on except the theme system. So that's the reason for my post.&nbsp;</p>
  151. <p>I work on the integration of my new module each evening until late at night, I'm a noon day sleeper. Anyhow, I have been completely rebuilding the process of designing themes. But until I complete the entire module I can't offer any of the 21 I have now for download. They won't work on any other Nuke site now.&nbsp;</p>
  152. <p>One thing I wanted to mention is the button maker I have on my site now. It produces the css3 code which can be inserted into your style sheet and called up as either a class or id in any container div, span, p. I use it all over my site. Take a look if you find some extra time on your hands, you don't need to be a member to use it.&nbsp;</p>
  153. <p>My thinking has always been if you have a website then all pages &nbsp;should look the same. I have a simple drop down menu now but that is going to change. I have an idea in mind that I may run with. There's no blocks like the ones we are used to I will be integrating side sliding content features. I have already coded them and just need to study over them some.</p>
  154. <p>I can build a nice theme in under 5 minutes. Well enough typing &nbsp;:)</p>
  155. <p>Cheers!</p>]]></description>
  156.            <author> [email protected] (kguske)</author>
  157.            <guid isPermaLink="false"></guid>
  158.        </item>
  159.    </channel>
  160. </rss>

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda