androbey

Members
  • Content count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About androbey

  • Rank
    Newbie
  1. Hi bernhard, thank you for your tips. You're right, using a workaround I could nearly get the desired outcome. However, I would say that both solutions come with a huge downside (uploading more images than necessary..) .
  2. I think it would be a great advantage for images to have an option to translate image tags, alongside the translatable description field (when using PWs language feature at all). This feature could improve the multi language support in ProcessWire even further, thus the usability of it. As a side effect that would also mean, that image tags could be easily used with the search engine, when dealing with a lot of images.
  3. Hi @heldercervantes, thanks for your reply. I see and I was afraid to hear that. Personally, I wouldn't have a big problem using extra fields for that purpose, but it looses a lot of usability for the actual client using the feature. As I am using the build in API to find images based on tags (and the capabilities that comes along with that), it would mean a huge loss for my current implementation. Thanks also for the hint to add it to the feature request list. Will add it there.
  4. Hello there, I was wondering if it's possible to somehow translate image tags. Right now I have a page which outputs all images related to one tag in a single container (as there are many tags this results in various containers). Every container has a title (and id) with the tag string, but currently only in the language of the entered tags. Using the PW format inside the code like this does, of course, not work.. _x($variable,'translated Tag') Is there a way to achieve this, without using workarounds (like extra fields)? Cheers, Andreas
  5. Thank you both, Robin S and wbmnfktr! I managed to achieve the desired behaviour by setting a GET Variable in the redirect URL and adjusted the code. I already did prepend the "_init.php" file, but was probably overwriting the session variable.. Here's the code I use in my "_init.php": if(!$user->isLoggedin()) { //'returnID' is my GET variable and page id 1055 is my start page (not log-in page). if(isset($_GET['returnID']) && $page->id!=1055 ){ $session->set('returnPage', $_GET['returnID']); } } Thanks again, you helped me a lot.
  6. Hi @wbmnfktr, thanks for your reply. That code works fine, but only with a condition, which is problem for my current setup. Pre-condition that psy's code works is that "_init.php" gets loaded at all. As far as I see, that file only get's loaded when user role "guest" has access to the corresponding template, but not if restricted permission (and so redirection) is set in ProcessWire backend. However, only certain user roles should have access to the template. As a workaround I could add permission handling in the specific template, but then I would loose control in ProcessWire backend as I would have to hardcode user roles. Maybe I'm wrong with this or do you know how to set "returnPage" variable before ProcessWire redirection?
  7. Hello everyone, I'm rather new in developing with ProcessWire and loving it every day more. I found that new module "LoginRegister", which is amazing. However, I would be happy about one feature. I wasn't able to solve this myself. Is there a possibility to achieve, that a user is redirected to a site (which is denied for guest users) he actually wants to view? Let's say I have a restricted sub-page called "test", which redirects to LoginRegister login form if a user is not logged-in. Right now, the redirection after successful log in is static and points to a pre defined site (let's say: "welcome"). So when a user tries to call mypage.com/test and logs in successful he gets to mypage.com/welcome instead of mypage.com/test.. Hope you have some hints for me on how to achieve this.