Jump to content

Timezone Issues

Fixed 1.1.7 1.2.0

etiv
etiv

Posted (edited)

Just purchased and went through the other threads to try and get a solution. I did utilize the timezones provided by Microsoft as you linked but I still get this error in console. 

 

[PurgeFX] Invalid timezone 'Central Standard Time' in config. Falling back to server default.
[PurgeFX] [ScheduleServerWipeCommand] Scheduling wipe at 11/06/2025 12:00:00
[PurgeFX] Invalid timezone 'Central Standard Time' in config. Falling back to server default.
[PurgeFX] [GetWipeDate] Using cached wipe date: 11/06/2025 12:00:00
[PurgeFX] Invalid timezone 'Central Standard Time' in config. Falling back to server default.
[PurgeFX] [GetPurgeStartDate] Using cached start date: 11/05/2025 18:00:00
[PurgeFX] [GetPurgeEndDate] Using cached end date: 11/06/2025 12:00:00
[PurgeFX] [GetWipeDate] Using cached wipe date: 11/06/2025 12:00:00
[PurgeFX] Invalid timezone 'Central Standard Time' in config. Falling back to server default.
[PurgeFX] Invalid timezone 'Central Standard Time' in config. Falling back to server default.
[PurgeFX] Invalid timezone 'Central Standard Time' in config. Falling back to server default.
[PurgeFX] Invalid timezone 'Central Standard Time' in config. Falling back to server default.

For context, I am running the latest version of Carbon and the underlying operating system is Ubuntu (although I tried unix timezones as well)

Any idea how I could fix it?

EDIT: Also for some added context, when I first loaded the plugin, GMT Standard Time gave me the same message. 

Edited by etiv
0xDEADBEEF

Posted

Noted. I will investigate and get back to you.

Thanks for letting me know!

etiv

Posted

38 minutes ago, 0xDEADBEEF said:

Noted. I will investigate and get back to you.

Thanks for letting me know!

No worries. I did try the previous version as well. Same issue in that one. 

SirApesALot

Posted

I also purchased this today and am having the same issue...

0xDEADBEEF

Posted

On 11/2/2025 at 11:42 AM, etiv said:

Just purchased and went through the other threads to try and get a solution. I did utilize the timezones provided by Microsoft as you linked but I still get this error in console. 

 

[PurgeFX] Invalid timezone 'Central Standard Time' in config. Falling back to server default.
[PurgeFX] [ScheduleServerWipeCommand] Scheduling wipe at 11/06/2025 12:00:00
[PurgeFX] Invalid timezone 'Central Standard Time' in config. Falling back to server default.
[PurgeFX] [GetWipeDate] Using cached wipe date: 11/06/2025 12:00:00
[PurgeFX] Invalid timezone 'Central Standard Time' in config. Falling back to server default.
[PurgeFX] [GetPurgeStartDate] Using cached start date: 11/05/2025 18:00:00
[PurgeFX] [GetPurgeEndDate] Using cached end date: 11/06/2025 12:00:00
[PurgeFX] [GetWipeDate] Using cached wipe date: 11/06/2025 12:00:00
[PurgeFX] Invalid timezone 'Central Standard Time' in config. Falling back to server default.
[PurgeFX] Invalid timezone 'Central Standard Time' in config. Falling back to server default.
[PurgeFX] Invalid timezone 'Central Standard Time' in config. Falling back to server default.
[PurgeFX] Invalid timezone 'Central Standard Time' in config. Falling back to server default.

For context, I am running the latest version of Carbon and the underlying operating system is Ubuntu (although I tried unix timezones as well)

Any idea how I could fix it?

EDIT: Also for some added context, when I first loaded the plugin, GMT Standard Time gave me the same message. 

The plugin has been rewritten in version 1.2.0 to use GMT offset numbers instead.
Please update your plugin and open a new ticket if you run into similar issue or others.

Thanks

0xDEADBEEF

Posted

Changed Status from Pending to Fixed

Changed Fixed In to 1.2.0

2.1m

Downloads

Total number of downloads.

9.7k

Customers

Total customers served.

141.2k

Files Sold

Total number of files sold.

3m

Payments Processed

Total payments processed.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.