Skip to content
TORNLIFE More

Difficulty with employees

Started by Overseer [2143302] on in Bugs & Issues.

33 replies · 682 views · thread synced · 6 days ago · View on torn.com
About this thread

Posts archived: 34 / 34 posts (100%) · the total is Torn's reply count + the opening post at the last fetch

Counted by TornLife from the archived posts.

Archived posts
34
Discussion span
→
Authority score
60 / 100
Historical score
39 / 100
Story score
52 / 100
Engagement score
72 / 100

People posting, likes and official posts are not counted for this thread yet: on threads longer than one page they come from a periodic pass over the archive, which has not covered it.

Most-liked replies

  • CloudJumper [1636201] · 6 likes ·
    The issue is occurring if you have at least one employee set to zero salary. If you wish to have a temporary workaround, make sure you set up a salary for all employees (1 dollar works too). Once you submit …
  • InDaHood [518368] · 4 likes ·
    All my employees have always been zero pay. It wasn’t an issue yesterday when everyone was zero pay so some code somewhere got updated badly. Why offer work around when the code could simply be fixed.
  • Overseer [2143302] · 2 likes ·
    It doesn't seem to require every salary to be at $1 if that signifies anything to you guys. I have 10 employees and when i entered the fifth** "1" the "Submit Changes" button popped out. Edit: **
Overseer [2143302] · #1 · edited
Hello I just went to hire a new employee i ran into several, probably linked, issues in this process.

To begin with, I was on the Android app, and could not update, train, or fire any of my employees.

[image: i.gyazo.com]
Following this, I switched to my laptop to see if i would have similar issues. I was able to fire the employee, i didn't test trains.

I am still, however, having issues positioning my new employee. I can change the dropdown from "Unassigned" to "Clerk" but I am unable to update the change with the Update button. Accepting the employee on my laptop did not seem to have the same issue. I cannot speak for it on the android.

[image: i.gyazo.com]
I'm unsure of anything that could cause this as far as actions that I have done.

Thanks! :)
Bennyh [157211] Officer Officer · #2 · edited
There appears to be caching issues after the update. Can you clear all of your cache and try again?
Theory [2190956] · #7
Same here. I use kiwi browser on mobile and can't do nothing on the employees tab. Trains are full, hope this gets sorted before tomorrow XD
The_savager [2243198] · #10
I’m using google chrome on iPhone 8 Plus everything up to date and signed out and cleared all temp files on chrome signed back in still nothing still same issue can’t change role/ wages / fire anyone it’s like I’m not the manager. And my company just lost 200k profit for today hell of a drop haha ?
Theory [2190956] · #11
Update: Switching to desktop mode and turning my phone sideways, I was able to train my employees. But still can't switch positions.
PsycWard [1579270] · #15
same issue

As a temporary fix, if you make your changes then select the submit button with inspect element you should get:
<button class="torn-btn disabled" disabled="">SUBMIT CHANGES</button>

After removing disabled from class and disabled="" I was able to submit changes for a minute or two.
<button class="torn-btn">SUBMIT CHANGES</button>
CloudJumper [1636201]Staff · #19
The issue is occurring if you have at least one employee set to zero salary.

If you wish to have a temporary workaround, make sure you set up a salary for all employees (1 dollar works too). Once you submit the changes, the buttons should be enabled.

Please also note that the system is not allowing the salary to be reverted to zero, if you implement the temporary fix, you will be stuck with at least one dollar salary per employee till the issue is completely resolved.

Thanks..!!
InDaHood [518368] · #20
All my employees have always been zero pay. It wasn’t an issue yesterday when everyone was zero pay so some code somewhere got updated badly.


Why offer work around when the code could simply be fixed.