You are not logged in.
I don't know if this is a symptom of the 4.1.7 and 4.2.1 update's changes to the upload field, or if it has always behaved this way and I didn't notice, or if it can even be classified a bug. But, any time I edit a module to change something, if there is a file already uploaded (an image in this case), it says that the image is required, and makes me re-upload and redo crops on the image, even if I didn't want to make changes to the upload field. It seems that this should see that there have been no changes made to the upload field, and leave the entry as it was. Thanks.
No problem, just checking. This is one of the more requested features from my editors, so I'll look into the /custom/admin/modules/dashboard/default.php technique.
I know I've seen mention of this before, but with the extensions capability in 4.2.1 this would probably be really easy to share. Can we have a file browser button in the Dashboard, so files and/or photos can be added without having to edit a content item to get to the file browser?
Gotta love secrets like that! The cache buster isn't super necessary. I'm not editing the CSS as much now that the site is live; that was more for development. Thanks.
I'm wondering if there is a good way to specify a content_css file for the TinyMCE editor. I had previously edited core > admin > js > main.js, and passed the following argument into the tinyMCE.init() function:
content_css : "/css/master.css?" + new Date().getTime()
Obviously, changing core files is not ideal. Is there a better way to do this that doesn't require modifying core files? I just updated, and am going through the motions of re-implementing these changes, but I figured I would check for a better solution first so I don't have to do this again in the future. Thanks.
I should have thought of that. Sorry for the confusion; everything seems to be working as expected.
I just had the same thought. I'm clearing the cache and will check to see if the issues clear up.
Update. The Developer>Media add button now seems to be working. I'm wondering if the click issues are stemming from cached javascript?
Hi there, I finally got some time to update to 4.2.1 and I'm noticing a few immediate issues.
Image cropping no longer works. When we attempt to resize images, the crop windows are no longer allowing us to specify crop boundaries. I noticed the new "Developer>Media" option in the dashboard menu, and I'm guessing there have been some changes to the way image resizing is handled, but when I press the "Add" button on the media page, nothing happens. So, I'm unable to explore this new feature, unless I'm not understanding something.
To try and see if perhaps changing the configuration options on the "Upload" field type might fix the aforementioned issue, and to see if the upload field type was somehow affected by the changes to new media handling, I attempted to configure the upload field in this particular module. Unfortunately, this field's blue wrench/screwdriver icon is not clickable. I then checked to see if any of the fields in this module were configurable, and clicking the icon does not seem to do anything for any fields. No context menu appears.
Also, we have noticed random inabilities to click icons. Clicking the archive button in one of our module's records was not responsive until the page was refreshed. It worked after a reload.
If I can elaborate on anything, please let me know. I've temporarily disabled some prominent features of the website, so I'm hoping these are known issues that can resolved fairly quickly ![]()
Oh yeah. Completely unnecessary. I think I did that before I had a good grasp on what the view parsers were used for. I deleted them.
Oh man, of course. I can't believe I didn't catch that. Thanks.
I also noticed your view parsers for each column were just a variable name -- not sure what the intention was there but it was throwing errors when caching.
Not sure what you mean here. Where would I look to see this?
It appears that a module (searchable list) view is excluding any records that have text columns with apostrophes in them. If I check out the database, the apostrophe's are being escaped correctly in the database.
These three rows are visible in the database, but not in the view.
'63', '...', '...', 'Director\'s Assistant/Employee Recruitment Coordinator', '', '', '[]', '[]', '[]', '[]', '[]', 'Staff', '...'
'89', '...', '...', 'Director\'s Administrative Clerk', '', '', '[]', '[]', '[]', '[]', '[]', 'Staff', '...'
'120', '...', '...', 'Student Health Clinic Physician\'s Assistant', '', '', '[]', '[]', '[]', '[]', '[]', 'Staff', '...'
Thanks Tim. That sounds perfect. I implemented it, and will test it out.
Any advice on how to deal with the browser caching of documents such as PDF's when you overwrite them with the "replace" option in the file manager? If the user doesn't force refresh the browser, it still appears as the older content.
For reference, this issue was caused by the existence of a $cms object that I created in another included template file. From what I understand, there is never really a need to manually create the $cms object, as all pages should inherit the $cms class, so I removed the object, and everything is happy.
Nope, just a draggable view. Everything seems perfect now. Not sure what happened. Most likely my fault though ![]()
I just deleted all of the position values in the DB, and started from scratch. Everything seems to be ok now. I may have put it in a weird state somehow. I'll let you know if it resurfaces.
Much better!
Thanks Tim, I'll look into it.
I'm using positioning in archiving in conjunction on an employment module. We have a list of jobs available, which are pool jobs, meaning they come and go, and always have the same format. For some reason when I archive those and reactivate them it messes up the position of the other items in the list. Afterward the remaining non-archived items are left in a weird state, where the position data in the table does not match what is show in the dashboard for the module, and reordering things doesn't seem to fix the issue. The position number in the table updates relative to what it thinks its value is, not what its visual order in the module view shows. Hopefully that makes sense. Let me know if you need clarification.
Just as a datapoint, it looks like the difference is that this is record within a module, not a content page. Should the edit icon not be showing up for module content perhaps?
When approving content in the Dashboard, the Edit button does not function.
I did notice that the formatting of the links for the approve and deny buttons differ from the edit icon.
Edit - /admin/dashboard/pending-changes/22/22/
Approve - /admin/dashboard/pending-changes/22/#46
Deny - /admin/dashboard/pending-changes/22/#46
When working in the dashboard, and clicking the icons in the far right column to approve content, or other misc. tasks, if you're clicking through them at a fast rate, the notifications will stack and cover up the clickable icons. This slows things down a bit, and can get a little annoying. Perhaps move the notifications to the left side, instead of the right?
Here's an example of what I'm seeing:
My mistake. It's in there.