WordPress.org

1. dguyen
   Member
   Posted 1 year ago #

   I fully understand how to make certain themes available to certain blogs in our network, but is there a way to make page templates I design available for certain blogs.

   If WP 3.xx did not create a "virtual" directory for each blog, I could go into the theme files and manually add the page-template.php file into the directory.

   Can someone offer any insight? Planning for the future, I'd like the blogs to reference a central directory for the page-template.php (so that if any changes were needed, only one file would need attention).

   Seeing if that each blog in the network had it's own functions.php file I could easily add a php include function with the appropriate file...

   I imagine andrea_r will be the first to remark? hmmm?

2. Andrea_r
   team pirate
   Posted 1 year ago #

   Page templates are theme dependent, so... how would have a central repository for them work with multiple themes? ;)

   It's also completely counter to how themes handle templates at the moment.

   Let's just assume for the moment that you're making really big & full page templates that completely override whatever theme is in use. (for the sake of argument, as it can be done...)

   Currently, you can't restrict access to a page template without restricting access to the theme itself. Not sure if an if statement at the top would work, as in "if this is blog #12, show this page template".

   For having one repo, you could also set up symlinks.

   whether or not it's a good idea is another question. :D

3. dguyen
   Member
   Posted 1 year ago #

   Thanks Andrea_r, you've confirmed my notions.

   I was hoping to create a parent theme for my network that included various page-templates. I wanted to make those page-templates only available to certain users who've paid for them. It looks as if, that's not going to happen.

   I guess I'll have to offer various themes with certain page-templates included.

   Thanks again Andrea_r

4. Andrea_r
   team pirate
   Posted 1 year ago #

   Can I take a wild stab of a guess that they contain squeeze pages? :D

5. dguyen
   Member
   Posted 1 year ago #

   No, no, no. No marketing here. I'm creating a site for people to display their portfolio of work (whatever they please, whether it's written, graphic designs, print, web, coding, etc...) and the different page-templates would allow the user to decide how that particular page is laid-out or styled.

   ie. Let's say the default theme only comes with a default-pagetemeplate. They want to display their "written" masterpiece, they could then purchase my writers-pagetemplate ($1) and then they also want to display their greeting card designs, so they could then purchase my printdesign-pagetemplate... now they would have access to two more page-templates.

   Does any of that make any sense? I like info graphics, my written explanations are not so concise...

6. dguyen
   Member
   Posted 1 year ago #

   My obstacles as you recognized were:

   • restricting access to paid user
   • allowing purchased page-templates to span multiple-themes

   I thought if there were a way for all the new themes to inherit a repository of page-templates (sorta like a child theme inherits the parent theme), then all I would need to work on is the "restricted access" part.

Topic Closed

This topic has been closed to new replies.