Jump to content

ferraky

Members
  • Content Count

    14
  • Joined

  • Last visited

Community Reputation

10 Good

About ferraky

  • Rank
    Jr. Member

Recent Profile Visitors

1,545 profile views
  1. Hey Everyone, I'm running into an issue when creating a new PageReference field type. Just creating the field and saving causes an exception to be thrown. Right before saving: https://www.dropbox.com/s/y4k7uw6dg5x1pmu/Screenshot 2017-11-25 09.27.13.png?dl=0 Right after saving: https://www.dropbox.com/s/gi9mbthg16fewc8/Screenshot 2017-11-25 09.27.28.png?dl=0 Running PW 3.0.83 Any ideas what might be going on?
  2. Thank you for the feedback. I feel like this is a lot of overhead for this approach right now. Hopefully things will get better around SEO and SPA websites. Thanks again!
  3. Just curious if anyone has used this or a similar approach in production? If so, can anyone post comments on hurdles, challenges etc...? I have a site I'm working on but am having second thoughts on this approach because of SEO, but I'm not sure if I should be concerned with SPA websites and SEO anymore.
  4. Hey Guys, Looking for a little help with working with the depth feature on the Repeater Matrix. I am working on building a page builder similar to the one discussed here: https://github.com/ryancramerdesign/ProcessWire/issues/1906. I am having a hard time looping over the Repeater Matrix and each item at each depth and combining them into a single array to present to the UI. The reason I am trying to push this to an array is because I am converting it to JSON for various Vuejs components that need to be supported. The structure of the "Builder" is: section: depth 0 - has various options that can be applied to a section of page( background image/color etc...) container: depth 1 row: depth 2 column: depth 3 - has various options for different widths for the column being set up. custom components: depth 4 - CKEditor, slider, whatever custom component that is needed Hopefully I am making sense explaining this. Any help would be greatly appreciated. Thanks Ya'll! Kyle
  5. Thanks for the feedback guys, much appreciated!
  6. Thanks for the feedback. I'll take a look at that scenario.
  7. Just wanted to share a new site that we launched earlier this week. http://www.enovity.com/
  8. Any more info on this? Anything we can do to help? Really looking forward to this.
  9. That did the trick! Thank you so much man, and thanks for the tip on ditching the get() calls. Never sure when and when not to use the get method. Thanks again, you're a life saver.
  10. After posting the above I realized that that page component actually isn't one thats having the issue. It looks like it is when I have a repeater on the page template. The below template/component is one that has the issue of not loading up the images initially when viewing the page in the dashboard. {% if data is null %} {% set data = page %} {% endif %} <article class="c-component c-content-block" {% if data.color %} style="background-color: {{ data.color }}" {% endif %}> {% for column in data.get('content_columns') %} <div class="c-content-block__column {{ data.collapse_mobile ? 'c-content-block__column--collapse' : '' }}" style="{{ column.width ? "width:" ~ column.width ~ "%;" : "width:50%;" }}"> {% if column.get('image') %} <figure><img src="{{ column.get('image').get('url') }}"></figure> {% endif %} {% if column.content %} {{ column.content }} {% endif %} {% if column.icon %} <span class="c-content-block__icon {{ column.icon }}"></span> {% endif %} </div> {% endfor %} </article>
  11. Hey felix, Here is some code from a couple of the templates that are used as page table page chunks. This is my image gallery template that is one of the templates that is having the issue. This template is loaded in a repeater on the front end hence the "data" var, but when on the backend I grab the current page. Let me know if you need more info and I can give read access to the bitbucket account I use. Thanks for your time! {% if data is null %} {% set data = page %} {% endif %} <article class="c-component c-image-gallery"> <h4 class="c-image-gallery__heading">{{ data.heading }}</h4> <ul class="c-image-gallery__list js-image-gallery"> {% for image in data.images %} <li class="c-image-gallery__item"> <a href="{{ image.url }}" data-effect="mfp-zoom-in" title="{{ image.description }}"> <img src="{{ image.size(120, 120).url }}"> </a> </li> {% endfor %} </ul> </article>
  12. Thanks LostKobraki for the response. I will try posting on their thread like you suggested. Thanks again!
  13. I must be doing something wrong to not get a single response. Any help is greatly appreciated.
  14. Hey guys, I am a long WP user and have recently been moving to PW for all my client sites and am LOVING it. Great work on the CMS guys. I am using the flexible content strategy with the PageTableExtended module along with the Twig and Dataproviders modules. I am running into an issue on the backend, when viewing a page that has various "page components/page tables" built up, the images show as broken links and any image methods ( like size ) will blow up the page. Once I open the page table and close it everything is good and the images show up. Below are a couple screenshots. This is a shot of when I first go into the page: https://www.dropbox.com/s/siixtkhe1qpgc3p/Screenshot%202015-06-06%2011.03.07.png?dl=0 This is a shot after I have clicked to edit the page and have exited out. https://www.dropbox.com/s/q9xjmp3fagcwig2/Screenshot%202015-06-06%2011.03.47.png?dl=0 You can see how it loads up the images like it has finally instantiated the page object or something. Hopefully this makes sense and I am explaining it well enough. Thanks in advance for any input as it is greatly appreciated.
×
×
  • Create New...