adrian

The same error also occurs when editing any admin pages, eg: Pages > Home > Admin > Pages > Search Awesome enhancements though Soma!

RE: 3 - You need to install the core module - "Page Clone". Simply go to Admin > Modules > Process > Page Clone > install

You guys are on fire - nice work Professors Soma and Pete

Hi Peter, Are you suggesting you'd like two copies of the file then - one with the original name and one with the new custom name? My initial thought on this is that it will be problematic when you go to delete an image, as one version would be left behind. Of course it would be possible to extend the file fieldtype to store the original filename as well and either do a redirect, or keep record of the second version of the file. If two physical files were stored, it could be linked when deleting so both are deleted. I think at the moment these options are beyond the scope of this module. I think it is doable, but I think there might be some further thinking required to make sure there aren't any other complicating issues. Can you please further explain your usage scenario for wanting to keep the original filename? Maybe that will better help me to figure out the best the approach.

In a bit of a rush, so not sure if this is definitely right, but saw your question and thought this might help: https://github.com/adrianbj/ProcessPageFieldSelectCreator/blob/master/ProcessPageFieldSelectCreator.module#L377 It seems like you are missing some config options in your page field, possibly the parent_id and/or template_id - these are what you would set on the Input tab when creating a page field through the admin. Hope that helps.

Thanks for the bug report. I was really only testing on the latest dev version of PW. I have just pushed a new version to github that seems to work fine with 2.3. Please test and let me know how you go with it. I really should do some more tweaks on the css for this module, but am waiting till PW 2.4 and the new default admin theme are released as stable.

Not exactly what you are looking for, but you could use this module: http://modules.processwire.com/modules/process-page-field-select-creator/ to create the page field and populate the categories. Might be of some help. You can paste comma separated values when entering the select options (Option 2).

Try this instead: $user = $session->login($username, $pass); if ($user->isLoggedin()) { echo 'logged in'; } That should get the user's details into the user variable straight away.

Hi Steve and welcome to PW. What you are looking for is the "TinyMCE Advanced Configuration Options" set of options on the Input tab of the field you are trying to set up (eg. body). You'll need to add "table" to the plugins field and then "tablecontrols" in one of the theme_advanced_buttons fields. Let us know how you make out with it.

Sorry for the session misinformation - I really wasn't thinking clearly apparently The php.ini setting you are looking for is: session.gc_maxlifetime setting. Definitely worth doing a: https://www.google.com.au/search?q=php+session+vs+cookie because there are lots of interesting difference and similarities between sessions and cookies that apparently can be confusing, although it really is quite simple

I have had similar issues in the past, but not for a while. I am running 2.3.7 - from a few days ago. Have you also tried manually deleting the row from the modules DB table, or is the uninstall still working properly and taking care of this? Other than that not sure - sorry!

Have you tried deleting all the module related items in the site/assets/cache folder?

Hi Eltom, I am not really sure why this worked for you before - maybe I am misunderstanding exactly what is happening. Sessions last until the browser is closed or the user leaves the site (ie a redirect back from Paypal). You'll need to use cookies or you could save the data in PW pages. I haven't ever used PayPal, but I assume they return some transaction number along with some identifier that you also sent them initially, which can be used to identify the purchase. Take a look at these links: http://cheatsheet.processwire.com/input/properties-and-methods/input-cookie/ http://davidwalsh.name/php-cookies http://www.thesitewizard.com/php/set-cookies.shtml You can also set and get cookies with javascript/jquery. This is a great little jquery plugin for making this simple as possible: https://github.com/carhartl/jquery-cookie Hope that helps.

In case you guys haven't seen it yet: http://ckeditor.com/demo#widgets New content blocks and captioned images etc. Might be a useful addition, although the default box is pretty ugly

jacmaes, Regarding adding users, is this what you are looking for: http://processwire.com/api/variables/user/ Look at the very last item on the page entitled: "Adding a new user with the guest role" If you are entering text and you don't want to allow spaces etc, look at sanitizing the input with one of the "name" options mentioned here: http://processwire.com/api/variables/sanitizer/

Ok, I have swapped out the timeout approach for a callback, so hopefully that will solve it in a much better way. I have pushed this fix to github and the module is also now approved in the modules directory, so you should be able to update much more easily now. Please let me know if that works now.

Can you do me a favor and try changing Line 15 of the .js file from 200 to 500 to see if that helps. The change from 100 to 200 seems to have made it work all the time at my end, but maybe there are other issues. EDIT: are you getting any related console errors?

Have you guys see this module from horst that makes this possible for pages: http://modules.processwire.com/modules/page-tree-add-new-childs-reverse/ I haven't thought through how difficult it would be to make this work for repeaters, but might be worth a look.

One more small update pushed to github to hopefully fix the ASM initialization issue. maba - would you please mind checking to see if the new rules now consistently work as ASM fields please? Thanks

Thank you very much for the troubleshooting. I was testing with 2.3.5 and it was working fine. I see that with 2.3.7 the button now has that new id, whereas with 2.3.5, it was the containing <li> that had that id, but the button itself had #Inputfield_submit. So I just pushed another update that lists both ids, comma separated so it should support old and new versions of PW. Thanks again for your help with this and please let me know if you find any other problems!

I am really sorry you are having trouble with this. I can save multiple rules here no problem. I just pushed a small update to make the format field "required", but obviously that isn't your issue. I am curious if you are having the same problem saving when using other/older themes, and also what browser/OS you are on. Do you get any logged errors, or does the rule just not appear when the page reloads?

Based on your screenshot, I see that you haven't entered anything in the "Filename Format" field. Since the rule can't do anything without this field, this is a required field - the only one of fields which is, and the rule won't save unless it is filled out. Can you please try again with that field filled out. Thanks

Thanks for the extra details. I know about the layout on the new theme - to be honest I haven't looked at this thoroughly yet as I wanted to make sure Ryan had finalized exactly what classes will be used in the layout of these things. I will definitely keep it on my list of things to tweak though. As for the ASM issue. It currently seems random - sometimes it works as expected and other times it doesn't work properly. Regardless, you can use the field like a normal multiselect field and it will work fine and be converted to an ASM on save. I will look into this when I have some more time and see if I can solve it more reliably. The key thing is that it shouldn't affect the ability of the module to work until I get it sorted.

Hi motionmindz and welcome! PW gives you ultimate flexibility to handle SEO however you would like, but it does do a lot of great things to help you along, including excellent clean and SEO friendly URLs to all pages. It also has the ability to handle custom URL segments, rather than using GET variables: http://wiki.processwire.com/index.php/URL_Segments You should definitely make use of the sitemap module to generate a sitemap that can be submitted to search engines through tools like Google's webmaster tools: http://modules.processwire.com/modules/markup-sitemap-xml/ Remember that one of the key components of SEO is good content and proper use of html tags, which is, and should be, up to you and your content creators. Hope that helps, but let us know if you have any more specific questions.

Hi motionmindz and welcome to PW. Are you referring what tina is doing starting at around 1:46 in the video? If so, she is simply using a repeater field (http://processwire.com/api/fieldtypes/repeaters/) to store the type, ID, and title. The code she has used in the template to display the video is probably something as simple as: foreach($page->media_items as $media_item){ echo '<iframe width="560" height="315" src="//www.youtube.com/embed/'.$media_item->media_id.'" frameborder="0" allowfullscreen></iframe>'; } Some other tools you might find useful for media types are: http://modules.processwire.com/modules/textformatter-video-embed/ http://modules.processwire.com/modules/process-get-video-thumbs/ http://processwire.com/talk/topic/4580-video-fieldtype/ http://modules.processwire.com/modules/textformatter-soundcloud-embed/ http://modules.processwire.com/modules/audio-mp3/ http://modules.processwire.com/modules/local-audio-files/ Hope that helps.