Jump to content
adrian

Custom Upload Names

Recommended Posts

I have an image field inside repeater along with some text fields. Is it possible to rename the image using 1 of those text fields?

Share this post


Link to post
Share on other sites
1 hour ago, PWaddict said:

I have an image field inside repeater along with some text fields. Is it possible to rename the image using 1 of those text fields?

I am sure support could be added for this. Any chance you feel like having a go at implementing it? Sorry I am juggling lots of different commitments right now, but I'll take a look when I can if you don't get to it first 🙂

Share this post


Link to post
Share on other sites
54 minutes ago, adrian said:

I am sure support could be added for this. Any chance you feel like having a go at implementing it? Sorry I am juggling lots of different commitments right now, but I'll take a look when I can if you don't get to it first 🙂

I don't know If I can do it but I will try.

  • Like 1

Share this post


Link to post
Share on other sites

Unfortunately I haven't figured it out yet. This could take me days to fully understand your module and currently can't spend more time on it as I need to finish 2 projects.

Share this post


Link to post
Share on other sites
21 hours ago, PWaddict said:

Unfortunately I haven't figured it out yet. This could take me days to fully understand your module and currently can't spend more time on it as I need to finish 2 projects.

Turns out it already works 🙂

Just use $repeaterPage instead of $page.

Let me know if it works ok for you.

  • Like 1

Share this post


Link to post
Share on other sites

Actually, an even better option is probably to use $filePage as this will automatically choose the field from the repeater if the image is uploaded to a repeater image field or the main $page if the image is uploaded to an image field on the main page. Does that make sense?

 

  • Like 1

Share this post


Link to post
Share on other sites
1 hour ago, adrian said:

Actually, an even better option is probably to use $filePage as this will automatically choose the field from the repeater if the image is uploaded to a repeater image field or the main $page if the image is uploaded to an image field on the main page. Does that make sense?

 

Yep. It works perfect. Thanks again.

Btw in case you don't know if re-order the rules and then press submit the re-order doesn't saved.

  • Like 1

Share this post


Link to post
Share on other sites
20 hours ago, PWaddict said:

Yep. It works perfect. Thanks again.

Great!

20 hours ago, PWaddict said:

Btw in case you don't know if re-order the rules and then press submit the re-order doesn't saved.

Thanks, not sure when that happened - probably newly broken in UiKit theme. Should be fixed now.

Share this post


Link to post
Share on other sites
34 minutes ago, adrian said:

Thanks, not sure when that happened - probably newly broken in UiKit theme. Should be fixed now.

It needs a simple fix to properly work. You're using cache busting on js & css files by using the module version.

You have to replace module's version to 111 otherwise we get this: ProcessCustomUploadNames.js?v=1 instead of ProcessCustomUploadNames.js?v=111

  • Like 1

Share this post


Link to post
Share on other sites
25 minutes ago, PWaddict said:

You have to replace module's version to 111

Or rather not cast the version to int for use in the query string. I had to make this change in several of my modules after I switched to semantic version numbers.

  • Like 2

Share this post


Link to post
Share on other sites
6 hours ago, PWaddict said:

It needs a simple fix to properly work. You're using cache busting on js & css files by using the module version.

You have to replace module's version to 111 otherwise we get this: ProcessCustomUploadNames.js?v=1 instead of ProcessCustomUploadNames.js?v=111

Sorry about that - fixed in the latest version.

  • Thanks 1

Share this post


Link to post
Share on other sites

Hi!
There is a problem trying to upload a file from a custom frontend.

PHP Warning: count(): Parameter must be an array or an object that implements Countable in ...\ProcessCustomUploadNames.module.php:176


I have this problem since v. 1.1.0. So I had to rollback to 1.0.9.

The file is saved on the disc but not on the database.

My setup is:
Apache 2.4
Php 7.2.6
PW 3.0.120

error-custom-upload-names.JPG

Share this post


Link to post
Share on other sites
6 minutes ago, adrian said:

@Crowdland Technology - please try the attached version. I don't have any time to test right at the moment. If that doesn't work as is, please also uncomment line 160.

 

ProcessCustomUploadNames.zip

Thank you Adrian, I tryed it and now the error is:
Parse error: syntax error, unexpected 'if' (T_IF) in D:\var\www\realhomecrm\site\assets\cache\FileCompiler\site\modules\ProcessCustomUploadNames\ProcessCustomUploadNames.module.php on line 177

Share this post


Link to post
Share on other sites
47 minutes ago, Crowdland Technology said:

Thank you Adrian, I tryed it and now the error is:
Parse error: syntax error, unexpected 'if' (T_IF) in D:\var\www\realhomecrm\site\assets\cache\FileCompiler\site\modules\ProcessCustomUploadNames\ProcessCustomUploadNames.module.php on line 177

Sorry, please try this one.

ProcessCustomUploadNames.zip

Share this post


Link to post
Share on other sites
8 hours ago, Crowdland Technology said:

It worked. Thank you!
Only this warning remaings but not sure why.


PHP Warning: filemtime(): stat failed for D:/var/www/realhomecrm/site/assets/files/1319/andorra-729795_1280.jpg in D:\var\www\realhomecrm\wire\core\Pagefile.php:524

I am not seeing anything like that, but it might be something specific to your frontend upload form - it looks to me like it is trying to access the old filename. Could you share the code you are using?

Is that error there in 1.0.9?

PS - I have update the module to the last version I sent to you above.

Share this post


Link to post
Share on other sites
4 hours ago, adrian said:

I am not seeing anything like that, but it might be something specific to your frontend upload form - it looks to me like it is trying to access the old filename. Could you share the code you are using?

Is that error there in 1.0.9?

PS - I have update the module to the last version I sent to you above.

Hi! The is no problem in version 1.0.9.

This is my code.

 

if (isset($_POST['galeria'])) {
	// process form input
	$formGaleria->processInput($input->post);

	if (!count($formGaleria->getErrors())) {
		// if no error occured
		// create new page and save values
		$uploadpage = $pages->findOne("template=db-propiedad,id=$idPropiedad");
		$uploadpage->of(false);
		$files = explode("|", $formGaleria->get("imagenes")->value);
		$targetWidth = 1024;
		$targetHeight = 768;
		foreach ($files as $file) {
			if ($file && file_exists($upload_path . $file)) {

				$filenameOrig = $file;
				$options = array('upscaling' => false, 'quality' => 100, 'sharpening' => 'soft');
				$imageSizer = new ImageSizer($upload_path.$filenameOrig, $options);
				$success = $imageSizer->resize($targetWidth, $targetHeight);
				if($success) {
					$uploadpage->imagenes->add($upload_path . $filenameOrig);
				}
				unlink($upload_path . $file);
			}
		}
		$uploadpage->save();
		$session->redirect($pages->get("/crm/propiedades/imagenes")->url . $idPropiedad);
	} else {
		// form incomplete or errors happened
		// we remove uploaded files
		$files = explode("|", $formGaleria->get("imagenes")->value);
		foreach ($files as $file) {
			if ($file && file_exists($upload_path . $file)) {
				unlink($upload_path . $file);
			}
		}
		$formGaleria->get("imagenes")->value = ''; // reset field value
	}
}

 

Share this post


Link to post
Share on other sites

@Crowdland Technology - thanks for posting that. I honestly think you should consider converting the upload form to be a little more ProcessWire-y. Take a look at the second set of code blocks (the ones that include the file field) in this post: https://processwire.com/talk/topic/3105-create-pages-with-file-upload-field-via-api/

I just tested CustomUploadNames with this approach and there are no errors. I think the problem you are having is related to unlinking, but it would be good to get confirmation on where that error you are seeing is originating from - a stack tracy from TracyDebugger should help with that - you might need to toggle strict mode on from the Panel Selector to get the trace because it's a warning rather than a fatal error.

 

 

Share this post


Link to post
Share on other sites

I have a repeater field with 12 repeater items and each item has an image field too. I've added the related rename rule on the module but when I save the page it only renames the top 3 items. I'm using the latest version (1.1.5).

EDIT: On another repeater with 5 repeater items everything is working properly. The only difference between those 2 repeaters is that the one with the 12 items is on a hidden page without a template file and it has svg images.

  • Like 1

Share this post


Link to post
Share on other sites
1 hour ago, PWaddict said:

I have a repeater field with 12 repeater items and each item has an image field too. I've added the related rename rule on the module but when I save the page it only renames the top 3 items. I'm using the latest version (1.1.5).

EDIT: On another repeater with 5 repeater items everything is working properly. The only difference between those 2 repeaters is that the one with the 12 items is on a hidden page without a template file and it has svg images.

Could you please narrow it down to whether it's due to no template file, the page being hidden, or because they're svg files?

 

Share this post


Link to post
Share on other sites
2 hours ago, adrian said:

Could you please narrow it down to whether it's due to no template file, the page being hidden, or because they're svg files?

None of the above is the problem. It seems that the module doesn't work well with repeaters. I tried to add new item on the repeater that is supposed to be working properly and it messed up that too. When I upload the image on the repeater item and saved the page the image gets renamed but I get just a broken blank image. 

In the files folder I'm getting the following images:

test_1544143931.-thumbnail.0x48n.jpg (Broken / blank)
test_1544143931.-thumbnail.300x0n.jpg (Broken / blank) This shouldn't be even there yet as I'm generating this variation via API and I didn't visit the frontend page during the test.

test_1544143934.260x0.jpg
test_1544143934.jpg
test_1544143934.-thumbnail.0x48n.jpg
test_1544143934.-thumbnail.jpg

Also if I try to delete that broken image from the image field that is inside the repeater item I'm getting this:

Quote

Warning: filemtime(): stat failed for C:/xampp/htdocs/mysite/site/assets/files/9091/test_1544143931.jpg in C:\xampp\htdocs\mysite\wire\core\Pagefile.php on line 541

 

  • Like 1

Share this post


Link to post
Share on other sites

@PWaddict - I have been testing here with repeaters a lot for the last few versions and it all seems to be working fine. Do you get the same issues on a new page starting from scratch? Just wondering if there are some effects of old images in existing repeaters instigated from an older version of this module?

Also wondering if your Filename Format setting is contributing to the problem - what are you currently using?

Share this post


Link to post
Share on other sites
3 minutes ago, adrian said:

@PWaddict - I have been testing here with repeaters a lot for the last few versions and it all seems to be working fine. Do you get the same issues on a new page starting from scratch? Just wondering if there are some effects of old images in existing repeaters instigated from an older version of this module?

All these days I was testing only with already uploaded images. I will test from scratch and will let you know.

4 minutes ago, adrian said:

Also wondering if your Filename Format setting is contributing to the problem - what are you currently using?

I thought that this could the problem but it isn't. On the filename format I tried even with just the word "test" and when I was saving the page only some of them were renamed and when I saved again and again more and more images were getting renamed to "test".

  • Like 1

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Robin S
      Repeater Images
      Adds options to modify Repeater fields to make them convenient for "page-per-image" usage. Using a page-per-image approach allows for additional fields to be associated with each image, to record things such as photographer, date, license, links, etc.
      When Repeater Images is enabled for a Repeater field the module changes the appearance of the Repeater inputfield to be similar (but not identical) to an Images field. The collapsed view shows a thumbnail for each Repeater item, and items can be expanded for field editing.
      Screencast

      Installation
      Install the Repeater Images module.
      Setup
      Create an image field to use in the Repeater field. Recommended settings for the image field are "Maximum files allowed" set to 1 and "Formatted value" set to "Single item (null if empty)". Create a Repeater field. Add the image field to the Repeater. If you want additional fields in the Repeater create and add these also. Repeater Images configuration
      Tick the "Activate Repeater Images for this Repeater field" checkbox. In the "Image field within Repeater" dropdown select the single image field. You must save the Repeater field settings to see any newly added Image fields in the dropdown. Adjust the image thumbnail height if you want (unlike the core Images field there is no slider to change thumbnail height within Page Edit). Note: the depth option for Repeater fields is not compatible with the Repeater Images module.
      Image uploads feature
      There is a checkbox to activate image uploads. This feature allows users to quickly and easily add images to the Repeater Images field by uploading them to an adjacent "upload" field.
      To use this feature you must add the image field selected in the Repeater Images config to the template of the page containing the Repeater Images field - immediately above or below the Repeater Images field would be a good position.
      It's recommended to set the label for this field in template context to "Upload images" or similar, and set the visibility of the field to "Closed" so that it takes up less room when it's not being used. Note that when you drag images to a closed Images field it will automatically open. You don't need to worry about the "Maximum files allowed" setting because the Repeater Images module overrides this for the upload field.
      New Repeater items will be created from the images uploaded to the upload field when the page is saved. The user can add descriptions and tags to the images while they are still in the upload field and these will be retained in the Repeater items. Images are automatically deleted from the upload field when the page is saved.
      Tips
      The "Use accordion mode?" option in the Repeater field settings is useful for keeping the inputfield compact, with only one image item open for editing at a time. The "Repeater item labels" setting determines what is shown in the thumbnail overlay on hover. Example for an image field named "image": {image.basename} ({image.width}x{image.height})  
      https://github.com/Toutouwai/RepeaterImages
      https://modules.processwire.com/modules/repeater-images/
    • By EyeDentify
      Hello There Guys.

      I am in the process of getting into making my first modules for PW and i had a question for you PHP and PW gurus in here.

      I was wondering how i could use an external library, lets say TwitterOAuth in my PW module.
      Link to library
      https://twitteroauth.com/

      Would the code below be correct or how would i go about this:
      <?PHP namespace ProcessWire; /* load the TwitterOAuth library from my Module folder */ require "twitteroauth/autoload.php"; use Abraham\TwitterOAuth\TwitterOAuth; class EyeTwitter extends WireData,TwitterOAuth implements Module { /* vars */ protected $twConnection; /* extend parent TwitterOAuth contructor $connection = new TwitterOAuth(CONSUMER_KEY, CONSUMER_SECRET, $access_token, $access_token_secret); */ public function myTwitterConnection ($consumer_key, $consumer_secret, $access_token, $access_token_secret) { /* save the connection for use later */ $this->twConnection = TwitterOAuth::__construct($consumer_key, $consumer_secret, $access_token, $access_token_secret); } } ?> Am i on the right trail here or i am barking up the wrong tree?
      I don´t need a complete solution, i just wonder if i am including the external library the right way.
      If not, then give me a few hint´s and i will figure it out.

      Thanks a bunch.

      /EyeDentify
    • By dimitrios
      Hello,
      this module can publish content of a Processwire page on a Facebook page, triggered by saving the Processwire page.
      To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers:
      Minimum Required Facebook App configuration:
      on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version (has been tested up to v3.3), add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "http://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. This module is configurable as follows:
      Templates: posts can take place only for pages with the defined templates. On/Off switch: specify a checkbox field that will not allow the post if checked. Specify a message and/or an image for the post.
      Usage
      edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, an access token is kept.
       
      Download
      PW module directory: http://modules.processwire.com/modules/auto-fb-post/ Github: https://github.com/kastrind/AutoFbPost   Note: Facebook SDK for PHP is utilized.


    • By kongondo
      FieldtypeRuntimeMarkup and InputfieldRuntimeMarkup
       
      Modules Directory: http://modules.processwire.com/modules/fieldtype-runtime-markup/
      GitHub: https://github.com/kongondo/FieldtypeRuntimeMarkup
      As of 11 May 2019 ProcessWire versions earlier than 3.x are not supported
      This module allows for custom markup to be dynamically (PHP) generated and output within a page's edit screen (in Admin).
       
      The value for the fieldtype is generated at runtime. No data is saved in the database. The accompanying InputfieldRuntimeMarkup is only used to render/display the markup in the page edit screen.
       
      The field's value is accessible from the ProcessWire API in the frontend like any other field, i.e. it has access to $page and $pages.
       
      The module was commissioned/sponsored by @Valan. Although there's certainly other ways to achieve what this module does, it offers a dynamic and flexible alternative to generating your own markup in a page's edit screen whilst also allowing access to that markup in the frontend. Thanks Valan!
       
      Warning/Consideration
      Although access to ProcessWire's Fields' admin pages is only available to Superusers, this Fieldtype will evaluate and run the custom PHP Code entered and saved in the field's settings (Details tab). Utmost care should therefore be taken in making sure your code does not perform any CRUD operations!! (unless of course that's intentional) The value for this fieldtype is generated at runtime and thus no data is stored in the database. This means that you cannot directly query a RuntimeMarkup field from $pages->find(). Usage and API
       
      Backend
      Enter your custom PHP snippet in the Details tab of your field (it is RECOMMENDED though that you use wireRenderFile() instead. See example below). Your code can be as simple or as complicated as you want as long as in the end you return a value that is not an array or an object or anything other than a string/integer.
       
      FieldtypeRuntimeMarkup has access to $page (the current page being edited/viewed) and $pages. 
       
      A very simple example.
      return 'Hello'; Simple example.
      return $page->title; Simple example with markup.
      return '<h2>' . $page->title . '</h2>'; Another simple example with markup.
      $out = '<h1>hello '; $out .= $page->title; $out .= '</h1>'; return $out; A more advanced example.
      $p = $pages->get('/about-us/')->child('sort=random'); return '<p>' . $p->title . '</p>'; An even more complex example.
      $str =''; if($page->name == 'about-us') { $p = $page->children->last(); $str = "<h2><a href='{$p->url}'>{$p->title}</a></h2>"; } else { $str = "<h2><a href='{$page->url}'>{$page->title}</a></h2>"; } return $str; Rather than type your code directly in the Details tab of the field, it is highly recommended that you placed all your code in an external file and call that file using the core wireRenderFile() method. Taking this approach means you will be able to edit your code in your favourite text editor. It also means you will be able to type more text without having to scroll. Editing the file is also easier than editing the field. To use this approach, simply do:
      return wireRenderFile('name-of-file');// file will be in /site/templates/ If using ProcessWire 3.x, you will need to use namespace as follows:
      return ProcessWire\wireRenderFile('name-of-file'); How to access the value of RuntimeMarkup in the frontend (our field is called 'runtime_markup')
       
      Access the field on the current page (just like any other field)
      echo $page->runtime_markup; Access the field on another page
      echo $pages->get('/about-us/')->runtime_markup; Screenshots
       
      Backend
       

       

       
      Frontend
       

×
×
  • Create New...