FireWire

Will do.

The culprit is ProDrafts. As soon as that was installed the image field started malfunctioning if it is outside of a FieldsetPage. So the FieldsetPage in PW version v3.0.77 and the current latest ProDrafts module v0.0.6 conflict.

Yeah I am working on localhost with a fresh install but may have missed testing. This was more on me for not being more thorough. The DB Backups is a go-to as it makes keeping a backup of the DB in the file system fast and reliable while keeping it inside the Git repo I'm working on. Helps coordinate the entire state of the code & CMS in one commit. @adrian I will look into those- good suggestion!

Alright. I re-stripped everything and it works. I'm going to go by one by one and test each module until I find the culprit. Will post if/when I can nail that down.

I did do that when I reinstalled to the latest dev. The only non-default module I have installed besides that is DB Backups so that I can jump around and test without losing info or work. I am trying again now.

My issue is that if a FieldsetPage is within the same tab as an image field, the image field won't upload. The image field is outside of the FieldsetPage. If my image field is inside a FieldsetPage, it works fine like yours does.

I'm out of ideas... installing/uninstalling that module made the difference for me. Is there anything else that could be doing it? A combination of things?

Final Update: I reinstalled 3.0.77 and went module by module. The issue is caused by using the new Fieldset (Page) module. I was really looking forward to using this new feature. Unfortunately enabling that module has an effect on image fields within tabs. I was using a Fieldset (Page) field in the same tab however moving it outside of that tab group did not solve the issue. Something that still has to be worked on I guess. Can also confirm that by uninstalling this module, the issue disappears. Bummed. This Fieldset (Page) module looks fantastic. Thanks everyone for their help!

Thanks. Will do. I wasn't too far into building out the cms so I started over. It does seem like ProDrafts would be the most likely culprit.

I've done many PW sites never an issue really an odd bug. Running a Docker instance with PHP7 & MariaDB 10.

Can't find anything out of the ordinary and the file shows up in the page assets file.

I'm checking and don't see anything out of the ordinary with respect to the other data around it. Then again I'm not 100% sure what to look for.

I don't believe so. I also downgraded to 3.0.76 just in case updating the core created an issue. Here is a list of my modules: FieldtypePhone FieldtapeRepeaterMatrix FieldtypeSelect FieldtypeTable FieldtyupeTextareas InputfieldCKEditor MarkupSEO MarkupSitemapXML PageEditSoftLock PageListShowPageId PasswordForceChange ProcessDatabaseBackups ProcessPageDelete ProcessRedirects ProcessWireUpgrade ProDrafts TemplateNotes TextformatterAutoLinks VersionControl

Hey everyone, I have an images field that is located within a Fieldset in Tab. When I add images it appears to upload them but when I publish the page they disappear. Here are some more details. The images are actually added (uploaded) to the page's asset directory but don't show up in the admin and aren't accessible from the API. Moving the field to the Content tab does not show the previously uploaded images, but it does allow you to add/upload images and they appear correctly. If you've entered images on the Content tab and move the field back to the other Fieldset in Tab, the images entered on the Content tab remain and are accessible via the API I've set and unset options for size requirements, for it's Formatted output value, etc. I have deleted the field, created a new one, and added it back to the tab- same issue. Basically tried everything I can think of and haven't run into this before. *Update* - Just found that the field doesn't work inside a regular Fieldset either. I'm out of ideas. Running PW v3.0.77

@Soma you have just saved me. Thank you.

Great find! Thanks!

Solved. @Zeka's suggestion to disable templateCompile solved all caching issues with class files. I was also using: spl_autoload_register() To dynamically load classes when they're called, unfortunately this doesn't seem to play well with PW. I used a regular include loop to add classes to app.php and it all works with namespacing. Big thanks to @abdus for the help!

I've added this to both app.php which loads the Class file, now it throws a new error saying that the class isn't found but it says that it's looking for the class in the template itself, instead of app.php it was looking for it before (the structure I noted above in my original post). Really trying to figure this out but it's throwing new errors and I'm doing some very basic things...

Alright- I've done that but I still get an issue with "Fatal error: Uncaught Error: Call to undefined function wire()" when called inside a class. I'm stuck on that.

I'm building a site that renders certain features using reusable classes. Unfortunately FileCompiler caches the files and my changes don't show up unless I clear the FileCompiler cache. On top of that, when I try to use the wire() function inside a class it throws a "Fatal error: Uncaught Error: Call to undefined function wire()". I've tried playing with ProcessWire namespacing, but have come up short. My files are structured as such: app.php - Is included in my templates and loads classes as they're called with spl_autoload_register. - classes/ExampleClass.class.php - Loaded by app.php Thanks!

PW Version: 2.7.2 PageTable Version: 0.1.3 Settings: The proper parent page is selected (Tickets) where this is a General Admission ticket. Admin field type to display in admin: title Page behaviors are all set to 'Nothing' Thanks for the help!

I am creating within the PageTable field and they are listed buy title. Can't get them to output on the front end either.

I'm working on adding a page with ticket information via a PageTable however when I add a page it creates it as a child page but does not show up in the PageTable itself. I've tried several times, checked that the pages allow children, etc. I'm logged in as a superuser and should have no issues and have seen no warnings on why the information isn't saving. There are 4 PageTables on this page and none of them are taking new additions. Any insight?

This is great. I am looking to find where in the page list it exists. I think that's possible with this plugin if I'm reading the documentation correctly.

I'm wondering if it's possible for an Inputfield Dependency to get a value from an inputfield on another page. Example: In the Admin I want an interior page to check if it's in a page selector field on the home page. If it's selected in the page selector on the home page, show a field. I haven't seen anything that would allow this but I'm hoping it exists.