Jump to content

mauricius

Members
  • Posts

    23
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by mauricius

  1. Ehy @teppo I'm really digging Wireframe and I really think that it's a brilliant work. Thank you also for mentioning my old TemplateEngineBlade module in the list of alternatives. I'm currently restyling one of my websites and I decided to use Wireframe for the purpose. Everything is going great so far! I also decided to create a renderer module that uses the Blade template engine, because I don't like Twig that much. Check it out https://github.com/mauricius/WireframeRendererBlade
  2. Nope, I got the same error. I'm trying to debug it right now. EDIT: I was able to figure it out. Apparently the saveConfig function is called from the following line in _sanitize_data, but the module is not present in the moduleIDs array inside Modules.php. if(json_encode($data) != json_encode($_data)) wire('modules')->saveConfig(self::clsname, $data); I temporarily removed this line from the module, then I installed it before putting it back. Now everything works correctly 👍
  3. Ehy @matjazp, I tried to install version 4.0.1 on a PW 3.0.148 and I got this error "Unable to find ID for module \AllInOneMinify". Do you have any idea what that means? Version 3.2.9 however works great! Thanks
  4. Unfortunately, as I said before, Jssor developers heavily changed the way to define animations in the markup, making the module almost useless. You can try with a previous version of the Jssor plugin. Sadly I don't have much time to work on a new version of the module and probably I would need to change the underlying plugin to something else.
  5. Thanks for your response. However the request gets redirected before even touching PW functions. Writing a die() instruction at the top of the ___processInput() function in InputfieldFile.module doesn't change a bit. I'm thinking that this problem is related somehow to the hosting provider and some obscure Apache directive. Non-ajax uploads work correctly.
  6. I have probably the same issue with an old PW 2.6 install on a shared hosting with PHP 5.5.32. The ajax upload completes with 100%, but I get Uncaught SyntaxError: Unexpected token < in the console. The problem is that the ajax request to admin/page/edit/?id=1067 ends with a 302 response code, therefore jQuery tries to parse the response of the root page, which obviously starts with <html>. I have the directive always_populate_raw_post_data set to Off, so I think that the problem is not related to https://github.com/ryancramerdesign/ProcessWire/issues/1174 and The directive upload_tmp_dir is set to /tmp/ with 755 permissions. No sign of errors in PW logs and messages. Anyone has clues?
  7. I think that 19 is the latest working version. Yesterday evening I tried with the new 20 version, but I noticed immediately that it was not working. In fact they removed the possibility to define caption animations directly in the markup (http://www.jssor.com/development/slider-with-caption-jquery.html) in favor of the new Jssor Slider Maker available on the website. At this point, with this new version, the module it's nearly useless. I could try to change how the module internally works, to reflect the new Jssor features, but I'm doubting that it will turn out as complete as the new Jssor Slider Maker.
  8. Yeah something might have changed in the last few months. As soon as I have a little bit of time I'm going to look into these recent issues with a new fresh PW 3 installation.
  9. You need to check if the Javascript code kicks in. Make sure to follow the instructions of the MarkupSlider module or make sure that you have all the JSSOR dependencies on your page.
  10. Unfortunately I haven't had the opportunity to play with PW 3 yet, so I don't know what's wrong here. Probably something is different in the way that PW fetches images. I'm quite busy by now, but I'll look into it as soon as possible, hopefully next week.
  11. Just check the Responsive/Full Width checkbox! However you still have to define the size of the slider in pixels. Ideally you should set the values based on the largest uploaded image.
  12. You have to make sure that the Jssor library is available in the folder /site/modules/ProcessSlider/jssor. Otherwise you can download it from the official website at http://jssor.com/download.html. The module uses only the files in the "js" and "img" folders, specifically the files "jssor.slider.debug.js" in development mode and "jssor.slider.min.js" in production.
  13. Thank you! Unfortunately this module doesn't use any ProcessWire fields (except for the images). It works only with HTML, therefore at this point building multilanguage sliders is nearly impossible. The only way you could build multilanguage sliders would be creating each time a new slider. However if you have access to your database you can easily use a little trick to speed up the process: add a new row in the slider table for each one of your languages. For example if you have German and English you can add two new rows (let's call them slider_de and slider_en) and you can copy and paste the code column to have the same settings as the original slider. Now you can translate your text in the administration section. As the last step you have to change the type of the Slider field from Slider to TextLanguage. In this way you can reference a different slider for each language, but remember that you have to type in the ID of the slider and not the name.
  14. I really don't know how to help you. Just make sure that $page->get('slider') returns a valid slider ID otherwise it will throw that error because you're trying to render NULL.
  15. I'm starting to think that the documentation is not clear enough on this point, I should definitely add more information. Let's try to explain better how the module works: Create your slider using the module, suppose that this slider is called Slider1. Define a field of type Slider and give it a name. I'm calling it slider. Add this field to an existing template, for example on the home template. Now go to your pages tree and edit the home page. On the slider field select the slider that you want to display on the page. On your template file use the code $page->get('slider') to get the ID of the Slider1 slider, and pass it to the MarkupSlider module.
  16. Make sure that the field that contains the ID of the slider is called exactly 'Slider1'. If you use only the instruction $page->get('Slider1'), without the module, it should print the ID of the slider.
  17. You're right! I'm going to fix it this afternoon. Thanks!
  18. Hi kongondo, I think the error is relative to the new module configuration introduced in ProcessWire 2.5.5 (https://processwire.com/blog/posts/new-module-configuration-options/) which is used by ProcessSlider and ProcessMarkup.
  19. The repository is available. See the first post for the link. It's in alpha-state however I'm already using it on my new personal website, which hopefully will be online tomorrow, so you can also take a look at the final result.
  20. Sure! I'm definetly going to write about it in a future blog post. It's my first project using Vue.js and I was very impressed with its potential, however the community is still quite small, so I had to figure out many things just by myself, especially regarding the implementation of sub-components, nevertheless I'm happy with the result. I'm planning to use it again in the future. Also thanks everyone for the warm welcome and positive reactions.
  21. Thanks everyone! @rick Yeah, as I said I'm planning to release the first alpha version in a couple of weeks, your feedback will be very welcome.
  22. ProcessSlider Module (alpha version) Repository https://github.com/mauricius/ProcessSlider Introduction Like many of you, I came to ProcessWire from Wordpress and immediately I fell in love with its power and its clean syntax. I have to say that PW has become my default choice for building websites. However there is only one thing that me and my clients miss from WordPress and is the ability to visually build image sliders through plugins (Nivo, Revolution Slider, LayerSlider, just to name a few). So I decided to create a module for this purpose. ProcessSlider essentialy is an editor for the wonderful Jssor plugin (http://www.jssor.com/) which is absolutely free. The module creates a new page under the Setup menu which allows users to easily add image sliders on the site using an intuitive visual editor. To each slider you can easily add images and other custom and animate them using the transition effects provided by the Jssor slider. The ProcessSlider module in reality is composed by three different modules: ProcessSlider: the main module InputfieldSlider/FieldtypeSlide: allows the user to use an existing slider inside a page MarkupSlider: converts the slider into Jssor compatible markup and optionally provides the necessary initialization script Features Custom slider size Drag and Drop interface Move and resize elements Slides background with images from existing PW pages Slider Preview (with the provided MarkupSlider module) Predefined style classes for Elements Add or remove Slides Add or remove elements Change slide order visually Jssor skins and bullets support Visual Timeline Optional responsive/fullwidth slider Predefined elements: Images, Text, Links, Image as link, Div blocks, Youtube Videos Animation Options (In and Out): Animation type, Delay, Duration The editor is built with Vue.js+Webpack and uses jQuery for D&D and resize functionalities. Release I'm going to release the module in a couple of weeks, there are still some minor tweaks and improvements that I would like to add. Demo Screencast (be sure to watch it at least at 720p) I hope it will be helpful to the community and I would be glad to get feedback or suggestions for improvement! Please also consider that it is my first PW module, so probably I'm missing some best practices, hopefully the most experienced developers can throw me some hints
×
×
  • Create New...