• Content count

  • Joined

  • Last visited

Community Reputation

6 Neutral

About cjx2240

  • Rank
    Jr. Member
  1. What's causing all my tweets to get truncated? $tweet[text] is trimmed at a set length and then outputs a link to the rest. Edit: The reason for this was that you need to request with tweet_mode => extended to get the new character limit from twitter. I was having a few other issues with this seemingly abandoned module and I needed this quickly so I ended up using another twitteroauth script instead and making my own. I assume to edit this into the module you'd add $params['tweed_mode'] = 'extended'; In MarkupTwitterFeed.module before the request on line 143, but I haven't tried it.
  2. Brilliant Module, very glad to have it.
  3. Same thing happened on my Invision forum and I was really unhappy with it! I sympathise.
  4. Thanks @abdus that looks great. Actually I was in a rush and I decided I would have to accept having a "/holding-page" and just used $session->redirect() but if I get a chance I will definitely change to this so I can be on "/"
  5. I've made a temporary new page on a new template, I want to redirect all traffic to this for a while, whilst making the url just be "/", what's the cleanest way to do this please?
  6. FieldsetPage seems like the perfect answer to this question I posted a little while ago, is this the kind of situation it was done in aid of? What I had been doing til now (based on chatter in that thread) was making RepeaterMatrixes, creating all the repeater items using a super user, then restricting access to the "move/copy/new" etc controls using CSS.
  7. I have updated mystyles.js to include another row with another style I have saved the file path in my field options I have cleared cache, refreshed, tried different browsers but nothing makes this list change: I also tried giving the file different name, and a different string within the file (still matching the filename, or not) The only way I could get it to work was by deleting the path in the field option and modifying mystyles.js in /wire, but obviously this isn't ideal.
  8. Updating RepeaterMatrix from 0.0.3 to 0.0.4 resolved the issue, thanks.
  9. Unfortunately, this just completely broke the field edit page for me!
  10. Thanks, you helped me find a bug in my own code that resolved my issue
  11. I am using this in a function on two websites. However on the second site, it returns nothing unless I am logged in in the front end. I'm assuming this must be some issue with permissions but I can't seem to track it down, everything looks the same between the two. Guests have only the standard permissions and "view-pages" is ticked - and the template of the page in question (and its parents) has no individual rules set. Anyone have a guess they could point me to?
  12. I tried this and it worked great! Thanks. I put it in admin.php. I targeted RepeaterMatrixes where the name ended in _fixed, as that appears as a class around the item. For anyone else who wants to use this, it's worth noting that it's important to have some if statement, if you just load it on every page you will get js errors when the file is called by ajax (eg image upload) I still think there's a place though for a simple field that contains fields, without allowing you to make as many as you want. It could also have the option to be put into tabs the way fieldgroup start/end currently works.
  13. @Macrura sorry but I think the way that Micro Contexts works is going over my head a little. Maybe a video would be good to explain how that works? I'm not suggesting that for my sake but just to get the idea across for other users! PageTable looks good but just like Table and RepeaterMatrix my problem is that you can make as many as you want, reorder them, delete them etc.. I just need something that is like a parent field, containing other fields. Perhaps using @Robin S's suggestion and hiding all the controls on a repeater matrix might be the answer....
  14. I have used that quite a lot, and it's suitable to this page in some ways, however, it allows the user to make as many of these sections as they want and re-order them, which leads to needing much more development on the front end to account for the items being in any order or missing altogether. Maybe a solution would be something like Limit Table (which I found indispensable for alleviating my original issue) - but for Repeater Matrix....
  15. Just wondering what everyone's approach is to a long page which requires many different pieces of input. For example, imagine your homepage is laid out like this: Banner Title Subtitle Multiple background images Links Second banner Title for area Paragraph of text Background image Bullet points Third text area Image Links List of feature with a title/description for each Call to action/banner Image Text Link News section introduction News section title Final call to action Title Description Link/link text List of partner logos Description List of images/links And most of these fields are not used on other parts of the site. Now, I can start of using a nice repeater matrix for banner images. I can use title, and then I can make a text field. I can make a text_2 and a text_3 and maybe a text_4 and I'm going to be able to reuse those in other templates too. I can make image, image_2 and the same thing applies. When it comes to a list of features, I might go with a ProFields Table. I have read Making efficient use of fields in ProcessWire - I found I was already using the advice within (a good read nonetheless) but still don't feel like my delivery is that efficient. Because a long list of fields like this is going to get incredibly busy and confusing. And is calling a lot of repeaters and a lot of different fields for this template alone going to slow the site down? Also there's a holdup every time you realise you need a new field and you have to go and create it, then save the template so you can select it. Is there a better way? I think I dream of some kind of unlimited "text" field that you can create as many of as you need to... (Not like ProFields Table, where the user can create as many as they want, but where the admin can make them on the fly while setting up the template) We could hardcode some of these small titles etc but in my opinion that will just quickly lead to the user asking "where do I change this line of text?" I could use a wysiwyg for areas of titles and descriptions but in my experience this quickly leads to broken layouts. I know this is very general but I wonder if people have a smart approach to this kind of template setup that I have not considered.