Jump to content

MadeMyDay

Members
  • Content Count

    362
  • Joined

  • Last visited

  • Days Won

    6

MadeMyDay last won the day on September 4 2014

MadeMyDay had the most liked content!

Community Reputation

569 Excellent

About MadeMyDay

  • Rank
    Sr. Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

8,752 profile views
  1. yeah sure, it's Open Source 😉
  2. Love it and cannot wait to try it 😎
  3. Honestly I have no clue what is happening there. Just out of curiosity, could you try to autoload the module? So in FieldtypePageTableExtended.module try 'autoload' => true (perhaps same for PageTable). Doesn't make that much sense but I have no idea why FieldtypePageTable isn't ready since it is already present. The modal injects its changes via ajax, I guess somehow there could be the problem with your referenced PTE template block. But its just wild guessing.
  4. could you share some more code, esp. how you render the blocks in your template and how that specific block with the page reference looks like. Thanks!
  5. Sorry, I never saw that error. You mean a page reference field? I also use page reference fields a lot so this shouldn't be the root cause. Do you have an another PTE field active in that template? I know there might be problems if there is more than one PT/PTE field in one template.
  6. I cannot install the module. Seems version 2.8. is left out in the compatible versions? Thx! edit: Nvmd, Manual Install works. Install via Classname didn't.
  7. I guess you are talking about the block and the corresponding detail page. You seem to put the text in the pte template. Why not put a page select field to the pte template and put the content of that textblock where it belongs, to the detail page (let's call it "summary"). Assuming your detail template is "detail" and the pte template is "pte_textblock". Add a page select to pte_textblock named "linkedPage". So in your pte_textblock template you have access to the fields of the detail page via $page->linkedPage->summary and also to the read more destination via $page->linkedPage->url. Ring a bell?
  8. Could you explain the use case for me? Why are those fields not filled in the details template and you just pull them to the PTE template? So the PTE template for example just consists of a page select field. You select a page and the PTE template renders the information pulled from that page.
  9. Sorry, I don't get it. You three different layouts for PTE, so far so good. Now you wanna do what? The read more link to a different page should point to a different template? Why not? For that URL the detail page template is used, isn't it?
  10. Hi @pwFoo, have you ever finished/published your module? Thx!
  11. Should be in core distribution. But you have to install it first. It is called "ProFields: PageTable" afair.
  12. I would say the PageTable module by Ryan is close to his repeater matrix ;-) I only extended the functionality of the former.
  13. See it as an alternative to the Repeater Module. For the repeater you define (the same) input fields for each item. The PageTable module is technically pretty similar as both store the items in own pages somewhere. But with the PageTable module you have the opportunity to use different templates as input field sets to choose from. The PageTable module shows those (sub)pages as a table with each page as a row. PTE extends that functionality for rendering the items as they are rendered in the frontend.
  14. Sure, why not? I am using it on more than ten websites. Some of them have thousands of visitors each day, but that is not the crucial thing since the module doesn't do anything different than the PageTable module itself. It "just" renders the templates also in the admin. There can be some glitches (as this thread shows) but as long it works for you in the admin area, it will also work for your visitors ;-)
×
×
  • Create New...