php code snippet in an html file?

Forums Forums All other PixoPoint plugins php code snippet in an html file?

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #1604
    foxed
    Member

    Just a quick question… trying to use the integration plugin with phpbb3.  I have the integration plugin configured now.  I’m editing the phpbb templates to integrate the code chunks but the code snippet is a <?php include which of course isn’t picked up by my phpbb header.html file. 

    Am I missing something?  How do I get the phpbb3 html theme files to work with <php snippets?

    #9031

    I don’t much about phpBB sorry. I don’t think they use a PHP based templating system so you probably need to use some other method to include the HTML, but I’m not certain.

    #9032
    Anonymous
    Member

    With phpBB I discovered that you can enable php parsing within the html template files via the phpBB admin control panel – Security Settings : Allow php in templates:

    You can then use the pixopoint tags within the template files (eg.overall_header.html)  using the following syntax

    <!– PHP –> include("…/chunk1.html"); <!– ENDPHP –>

    I have it generating the chunks now but not sure if there’s a bug in pixopoint now.  The plugin page doesn’t seem to save that I only want the chunks generated from a specific page.  The page name box is always empty.  I would also like to be able to tell it to manually update so that I can switch it off for general use.  Reason being… I’m getting weird duplicate chunks created if they are built from different pages.

    #9033
    Anonymous
    Member

    With phpBB I discovered that you can enable php parsing within the html template files via the phpBB admin control panel – Security Settings : Allow php in templates:

    You can then use the pixopoint tags within the template files (eg.overall_header.html)  using the following syntax

    <!– PHP –> include("…/chunk1.html"); <!– ENDPHP –>

    I have it generating the chunks now but not sure if there’s a bug in pixopoint now.  The plugin page doesn’t seem to save that I only want the chunks generated from a specific page.  The page name box is always empty.  I would also like to be able to tell it to manually update so that I can switch it off for general use.  Reason being… I’m getting weird duplicate chunks created if they are built from different pages.

    #9034
    Anonymous
    Member

    With phpBB I discovered that you can enable php parsing within the html template files via the phpBB admin control panel – Security Settings : Allow php in templates:

    You can then use the pixopoint tags within the template files (eg.overall_header.html)  using the following syntax

    <!– PHP –> include("…/chunk1.html"); <!– ENDPHP –>

    I have it generating the chunks now but not sure if there’s a bug in pixopoint now.  The plugin page doesn’t seem to save that I only want the chunks generated from a specific page.  The page name box is always empty.  I would also like to be able to tell it to manually update so that I can switch it off for general use.  Reason being… I’m getting weird duplicate chunks created if they are built from different pages.

    #9035
    &quot;lostfox&quot; wrote:
    I would also like to be able to tell it to manually update so that I can switch it off for general use.  Reason being… I’m getting weird duplicate chunks created if they are built from different pages.

    You should set a page or post ID in the settings page to make sure it isn’t using different templates sporadically.

    Alternatively, you can just disable the plugin. The files aren’t deleted on deactivation so will keep working even when the plugin is not activated.

    #9036
    Anonymous
    Member

    I tried limiting the chunk generation to a single page but the setting never seems to be saved.  Go back in and the field is empty and the chunks generate on any page hit.  I’d prefer to keep it active but limit it to a specific page.  Any ideas?

Viewing 7 posts - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.