<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title><![CDATA[PunBB Forums — Integrating PunBB into a generic CMS]]></title>
		<link>https://punbb.informer.com/forums/topic/21016/integrating-punbb-into-a-generic-cms/</link>
		<atom:link href="https://punbb.informer.com/forums/feed/rss/topic/21016/" rel="self" type="application/rss+xml" />
		<description><![CDATA[The most recent posts in Integrating PunBB into a generic CMS.]]></description>
		<lastBuildDate>Mon, 30 Mar 2009 16:50:17 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: Integrating PunBB into a generic CMS]]></title>
			<link>https://punbb.informer.com/forums/post/126238/#p126238</link>
			<description><![CDATA[<p>URL changed to:<br /><a href="http://www.pepak.net/files/punbb/studna.zip">http://www.pepak.net/files/punbb/studna.zip</a></p><p>This one should be permanent.</p>]]></description>
			<author><![CDATA[null@example.com (pepak)]]></author>
			<pubDate>Mon, 30 Mar 2009 16:50:17 +0000</pubDate>
			<guid>https://punbb.informer.com/forums/post/126238/#p126238</guid>
		</item>
		<item>
			<title><![CDATA[Re: Integrating PunBB into a generic CMS]]></title>
			<link>https://punbb.informer.com/forums/post/126131/#p126131</link>
			<description><![CDATA[<p>Hmm, looks like the readme file is gone. Will have to rewrite it sometime.</p><p>Meanwhile, the extension is here: <a href="http://www.pepak.net/files/punbb-studna.zip">http://www.pepak.net/files/punbb-studna.zip</a></p><p>Basically, what needs to be done:<br />1) The extension should be unpacked in your &lt;b&gt;extensions&lt;/b&gt; directory<br />2) Files in &lt;b&gt;modified&lt;/b&gt; should replace original PunBB files. The changes are minimal (just compare the files) but need to be done.<br />3) Queries and URLs in &lt;b&gt;manifest.xml&lt;/b&gt; need to be rewritten for your users-table and your URLs. Our engine is based on a really prehistoric PHP-Nuke. The whole point of this extension is that it isolates all references to user tables so that they can be modified easily.<br />4) Update your users table to contain all PunBB fields that are not present in your current table.<br />5) &lt;b&gt;all_users_fields&lt;/b&gt; contain a fieldset part of a SELECT statement that returns all fields in users-table. You will notice that for the most part, it is just &quot;my field renamed to PunBB field&quot;, with a few special cases (e.g. PHP-Nuke used a really stupid user_regdate format).<br />6) &lt;b&gt;users_fields_translate.php&lt;/b&gt; contain a translation layer between PunBB fieldnames and your users-table&#039;s fieldnames.</p>]]></description>
			<author><![CDATA[null@example.com (pepak)]]></author>
			<pubDate>Thu, 26 Mar 2009 21:24:50 +0000</pubDate>
			<guid>https://punbb.informer.com/forums/post/126131/#p126131</guid>
		</item>
		<item>
			<title><![CDATA[Re: Integrating PunBB into a generic CMS]]></title>
			<link>https://punbb.informer.com/forums/post/126130/#p126130</link>
			<description><![CDATA[<div class="quotebox"><cite>pepak wrote:</cite><blockquote><p>Don&#039;t expect an easy and effortless plugin - you <strong>will</strong> have to do a lot of work. The point is that you no longer need to search the whole source code to find the places that need to be changed.</p><p>Download it here: <a href="http://www.pepak.net/tmp/studna_punbb.zip">http://www.pepak.net/tmp/studna_punbb.zip</a></p><p>I provided a short readme file with details on what needs to be done. I would definitely suggest trying it out on your local copy of your site first, and do consider it an alpha code - I am sure I missed a parenthesis or a semicolon here and there... The important parts of the forum seem to work, though.</p><p>If you find any errors or improvements, I would appreciate hearing about them.</p><p>(The extension is called &quot;Studna&quot; because it is intended for our horror-movie site <a href="http://www.studna.net">Studna</a>.)</p></blockquote></div><p>Sorry to be bumping an older thread, but I found this thread and was wondering if pepak would be so kind as to re-upload his example plugin studna_punbb.zip</p><p>The url is a 404 now <img src="https://punbb.informer.com/forums/img/smilies/smile.png" width="15" height="15" alt="smile" /></p>]]></description>
			<author><![CDATA[null@example.com (stewart)]]></author>
			<pubDate>Thu, 26 Mar 2009 17:54:55 +0000</pubDate>
			<guid>https://punbb.informer.com/forums/post/126130/#p126130</guid>
		</item>
		<item>
			<title><![CDATA[Re: Integrating PunBB into a generic CMS]]></title>
			<link>https://punbb.informer.com/forums/post/124615/#p124615</link>
			<description><![CDATA[<p>Don&#039;t expect an easy and effortless plugin - you <strong>will</strong> have to do a lot of work. The point is that you no longer need to search the whole source code to find the places that need to be changed.</p><p>Download it here: <a href="http://www.pepak.net/tmp/studna_punbb.zip">http://www.pepak.net/tmp/studna_punbb.zip</a></p><p>I provided a short readme file with details on what needs to be done. I would definitely suggest trying it out on your local copy of your site first, and do consider it an alpha code - I am sure I missed a parenthesis or a semicolon here and there... The important parts of the forum seem to work, though.</p><p>If you find any errors or improvements, I would appreciate hearing about them.</p><p>(The extension is called &quot;Studna&quot; because it is intended for our horror-movie site <a href="http://www.studna.net">Studna</a>.)</p>]]></description>
			<author><![CDATA[null@example.com (pepak)]]></author>
			<pubDate>Sat, 14 Feb 2009 14:56:57 +0000</pubDate>
			<guid>https://punbb.informer.com/forums/post/124615/#p124615</guid>
		</item>
		<item>
			<title><![CDATA[Re: Integrating PunBB into a generic CMS]]></title>
			<link>https://punbb.informer.com/forums/post/124578/#p124578</link>
			<description><![CDATA[<p>Hi!</p><p>I am very interested in this, would it be possible to get the extension now? (or perhaps a beta release? <img src="https://punbb.informer.com/forums/img/smilies/wink.png" width="15" height="15" alt="wink" /> )</p><p>Best regards,</p>]]></description>
			<author><![CDATA[null@example.com (Cod)]]></author>
			<pubDate>Fri, 13 Feb 2009 23:05:03 +0000</pubDate>
			<guid>https://punbb.informer.com/forums/post/124578/#p124578</guid>
		</item>
		<item>
			<title><![CDATA[Re: Integrating PunBB into a generic CMS]]></title>
			<link>https://punbb.informer.com/forums/post/124544/#p124544</link>
			<description><![CDATA[<p>OK, my merging of PunBB 1.3 with a generic CMS is almost complete. It turns out the two changes above are the only ones that need to be done - other than that, everything can be handled with hooks.</p><p>I&#039;ll need to do some more testing (at the moment it seems everything is working fine, but of course the users will surely find some missing brackets or semicolons). After that, I will see about releasing the extension; of course it will be useless on its own, but it should be reasonably simple to adapt it to your particular CMS.</p>]]></description>
			<author><![CDATA[null@example.com (pepak)]]></author>
			<pubDate>Fri, 13 Feb 2009 15:26:20 +0000</pubDate>
			<guid>https://punbb.informer.com/forums/post/124544/#p124544</guid>
		</item>
		<item>
			<title><![CDATA[Integrating PunBB into a generic CMS]]></title>
			<link>https://punbb.informer.com/forums/post/123867/#p123867</link>
			<description><![CDATA[<p>I am currently writing an extension that will let me integrate PunBB to a content management system I use - basically, I want to use _my_ table of users, not PunBB&#039;s. Most of the stuff is easily done using hooks, but there are several changes that need to be done to the PunBB itself:</p><p>1) Database abstraction layer classes need to have a more detailed query_build parameters. Specifically, it is important to be able to use different prefixes for different tables, even within the same SELECT. As of now, there is only choice between all prefixes or no prefixes. I propose a change from:<br /></p><div class="codebox"><pre><code>if (isset($query[&#039;SELECT&#039;]))
{
    $sql = &#039;SELECT &#039;.$query[&#039;SELECT&#039;].&#039; FROM &#039;.((isset($query[&#039;PARAMS&#039;][&#039;NO_PREFIX&#039;])||(isset($query[&#039;PARAMS&#039;][&#039;FROM_NO_PREFIX&#039;])) ? &#039;&#039; : $this-&gt;prefix).$query[&#039;FROM&#039;];

    if (isset($query[&#039;JOINS&#039;]))
    {
        foreach ($query[&#039;JOINS&#039;] as $cur_join)
            $sql .= &#039; &#039;.key($cur_join).&#039; &#039;.((isset($query[&#039;PARAMS&#039;][&#039;NO_PREFIX&#039;])||isset($cur_join[&#039;PARAMS&#039;][&#039;NO_PREFIX&#039;])) ? &#039;&#039; : $this-&gt;prefix).current($cur_join).&#039; ON &#039;.$cur_join[&#039;ON&#039;];
    }</code></pre></div><p>to<br /></p><div class="codebox"><pre><code>if (isset($query[&#039;SELECT&#039;]))
{
    $sql = &#039;SELECT &#039;.$query[&#039;SELECT&#039;].&#039; FROM &#039;.(isset($query[&#039;PARAMS&#039;][&#039;NO_PREFIX&#039;]) ? &#039;&#039; : $this-&gt;prefix).$query[&#039;FROM&#039;];

    if (isset($query[&#039;JOINS&#039;]))
    {
        foreach ($query[&#039;JOINS&#039;] as $cur_join)
            $sql .= &#039; &#039;.key($cur_join).&#039; &#039;.(isset($query[&#039;PARAMS&#039;][&#039;NO_PREFIX&#039;]) ? &#039;&#039; : $this-&gt;prefix).current($cur_join).&#039; ON &#039;.$cur_join[&#039;ON&#039;];
    }</code></pre></div><p>2) User authentication functions in include/functions.php need a lot more hooks than they have now. The following parts should be optional, based on a hook response:<br />- Cookie expiration<br />- Cookie hash validation<br />E.g. something like:<br /></p><div class="codebox"><pre><code>$check_expiration = TRUE;
$validate_expiration_hash = TRUE;
($hook = get_hook(&#039;fn_cookie_login_validations&#039;)) ? eval($hook) : null;
if ($check_expiration) ...</code></pre></div><p>I will post more if (when) I find them.</p>]]></description>
			<author><![CDATA[null@example.com (pepak)]]></author>
			<pubDate>Sat, 31 Jan 2009 14:18:03 +0000</pubDate>
			<guid>https://punbb.informer.com/forums/post/123867/#p123867</guid>
		</item>
	</channel>
</rss>
