Jump to content

bobbintb

Members
  • Posts

    1,396
  • Joined

  • Last visited

Everything posted by bobbintb

  1. I've been having lots of USB issues since I upgraded my hardware and I'm just now realizing there has been a longstanding issue with Ryzen and USB. I'm starting to wonder how many USB issues on this forum are related to that.
  2. I know I'm a little late with the reply but there are two ways to do that. As mentioned, qemu/kvm can emulate a USB device. You can also do it natively in Linux but it has to be enabled in the kernel and that would require recompiling the kernel. But there are better ways to accomplish what you were trying to do that have been mentioned.
  3. No but here's what the documentation says: -e EMAIL_SMTP=True \ -e EMAIL_SMTP_HOST=TODO \ -e EMAIL_SMTP_PORT=TODO \ -e EMAIL_SMTP_USER=TODO \ -e EMAIL_SMTP_PASSWORD=TODO \ -e EMAIL_SMTP_USE_TLS= \
  4. For anyone unable to access the webui, you need to change the URL/BASEROW_PUBLIC_URL variable to your server ip/name and port.
  5. I did use a guide, or a least part of one. It will be included in version 6.13, as mentioned. I do have a compiled version on github: https://github.com/bobbintb/unRAID-audit But fair warning, I haven't looked at it in a while so I am not sure how out of date it is.
  6. Pretty much what the title says. ngix now gives 404 if I try to access the webui locally. Is there a way to change it back, hopefully without rebooting?
  7. I am working on a plugin and while I am testing I need to recompile the kernel. I had automation all set up for this but something has changed and now I cannot download the latest UnRAID automatically. Previously I would get the latest version from a link like this: https://unraid-dl.sfo2.cdn.digitaloceanspaces.com/stable/unRAIDServer-6.12.6-x86_64.zip I would just programmatically change the name of the zip file. Older versions still download but I can't get newer version. Any idea how I can resolve this? The download links on the website have some sort of long hash string in the URL so that won't work either.
  8. I think there are still some things that need to be cleaned up from the old wiki. Try the Wayback Machine: https://web.archive.org/web/20190805074914/https://wiki.unraid.net/index.php/UnRAID_6/VM_Management#Using_a_physical_disk_in_a_VM.2C_including_one_with_an_OS_already_installed
  9. I know this is an old topic but I think it's still relevant. I was recently looking at improving my process. I was looking at pre-commit (https://pre-commit.com/) but it's a little more complex than I want at the moment. Currently, I use github and have a master branch and a release branch. I set up a github action so that when I make a commit to the master branch, it will automatically package the txz, get the hash, and update it in the plg file, along with the version number and appending the commit message as the change log. It then pushes to the release branch. I had to make another branch to avoid an infinite loop scenario. The other issue is that if I need to make changes to the plg file, I need to make them on the release branch. But it saves a lot of time. Using pre-commit would solve that minor issue but it's just not the time setting it up at the moment.
  10. I managed to enable the Linux Audit Framework for unRAID but unfortunately it requires rebuilding the kernel. It's a simple flag in the .config file when building and I don't think there is really any downside or performance hit to having it available since the package would still need to be installed to use it. I think it would be beneficial to enable this for unRAID as it open the door for a more community development. I'm working on one right now that would benefit greatly from being able to track file system changes.
  11. You'd probably have to write a script that uses itnotify for that.
  12. I'm hoping for auditd support as well. There are things I have in mind that just aren't doable without it.
  13. I reordered some and it still says the autostart is out of order.
  14. I've got this function in my page file that runs a python script using the built-in `StartCommand.php` from the webui: function scan(cmd,title,plg,func,start=0,button=0) { // start = 0 : run command only when not already running (default) // start = 1 : run command unconditionally // button = 0 : show CLOSE button (default) // button = 1 : hide CLOSE button $('#scan-button').prop('disabled', true); $('#scanDir').prop('disabled', true); $('#dbDir').prop('disabled', true); nchan_plugins.start(); $.post('/webGui/include/StartCommand.php',{cmd:cmd+' nchan',start:start},function(pid) { if (pid==0) { nchan_plugins.stop(); $('div.spinner.fixed').hide(); $(".sweet-alert").addClass('alert'); return; } swal({title:title,text:"<pre id='swaltext'></pre><hr>",html:true,animation:'none',showConfirmButton:button==0,confirmButtonText:"<?=_('Close')?>"},function(close){ nchan_plugins.stop(); $('div.spinner.fixed').hide(); $('.sweet-alert').hide('fast'); setTimeout(function(){bannerAlert("<?=_('Attention - scanning continues in background')?> ["+pid.toString().padStart(8,'0')+"]<i class='fa fa-bomb fa-fw abortOps' title=\"<?=_('Abort background process')?>\" onclick='abortScan("+pid+")'></i>",cmd,plg,func,start);}); }); $('button.confirm').prop('disabled',button!=0); }); } When I run the python script in the terminal during development, everything looks great. https://github.com/bobbintb/UnRAID-DeDuper/blob/release/src/scripts/main.py But when I test it in UnRAID in the webui, there are all kinds of character encoding issues. I don't really know how to deal with that in the webui side of things as I'm still kind of new at web development. Instead of the neatly displayed progress bars (2), I get something like this: 0%|�[34m �[0m| (30.4G 0%|�[34m �[0m| 0.00/11.9G�[ 1%|�[34m▍ �[0m| 122M/11.9G�[A 0%|�[34m▏ �[0m|, 0/116 (30.4G 2%|�[34m▉ �[0m| 244M/11.9G�[A 1%|�[34m▍ �[0m|, 0/116 (30.4G 3%|�[34m█▍ �[0m| 366M/11.9G�[A 1%|�[34m▋ �[0m|, 0/116 (30.4G 4%|�[34m█▉ �[0m| 488M/11.9G�[A 2%|�[34m▊ �[0m|, 0/116 (30.4G 5%|�[34m██▍ �[0m| 609M/11.9G�[A 2%|�[34m█ �[0m|, 0/116 (30.4G 6%|�[34m██▉ �[0m| 731M/11.9G�[A 3%|�[34m█▎ �[0m|, 0/116 (30.4G 7%|�[34m███▍ �[0m| 853M/11.9G�[A 3%|�[34m█▍ �[0m|, 0/116 (30.4G 8%|�[34m███▉ �[0m| 975M/11.9G�[A 3%|�[34m█▋ �[0m|, 0/116 (30.4G 9%|�[34m████▍ �[0m| 1.07G/11.9G�[A 4%|�[34m█▉ �[0m|, 0/116 (30.4G 10%|�[34m████▉ �[0m| 1.19G/11.9G�[A 4%|�[34m██ �[0m|, 0/116 (30.4G 11%|�[34m█████▍ �[0m| 1.31G/11.9G�[A 5%|�[34m██▎ �[0m|, 0/116 (30.4G 12%|�[34m█████▉ �[0m| 1.43G/11.9G�[A 5%|�[34m██▌ �[0m|, 0/116 (30.4G 13%|�[34m██████▍ �[0m| 1.55G/11.9G�[A 5%|�[34m██▋ �[0m|, 0/116 (30.4G 14%|�[34m██████▉ �[0m| 1.67G/11.9G�[A 6%|�[34m██▉ �[0m|, 0/116 (30.4G 15%|�[34m███████▍ �[0m| 1.79G/11.9G�[A 6%|�[34m███▏ �[0m|, 0/116 (30.4G 16%|�[34m███████▉ �[0m| 1.90G/11.9G�[A 7%|�[34m███▎ �[0m|, 0/116 (30.4G 17%|�[34m████████▍ �[0m| 2.02G/11.9G�[A 7%|�[34m███▌ �[0m|, 0/116 (30.4G 18%|�[34m████████▉ �[0m| 2.14G/11.9G�[A 8%|�[34m███▊ �[0m|, 0/116 (30.4G 19%|�[34m█████████▍ �[0m| 2.26G/11.9G�[A 8%|�[34m███▉ �[0m|, 0/116 (30.4G 20%|�[34m█████████▉ �[0m| 2.38G/11.9G�[A 8%|�[34m████▏ �[0m|, 0/116 (30.4G 21%|�[34m██████████▍ �[0m| 2.50G/11.9G�[A 9%|�[34m████▍ �[0m|, 0/116 (30.4G 22%|�[34m██████████▉ �[0m| 2.62G/11.9G�[A 9%|�[34m████▋ �[0m|, 0/116 (30.4G 23%|�[34m███████████▍ �[0m| 2.74G/11.9G�[A 10%|�[34m████▊ �[0m|, 0/116 (30.4G 24%|�[34m███████████▉ �[0m| 2.86G/11.9G�[A 10%|�[34m█████ �[0m|, 0/116 (30.4G 25%|�[34m████████████▍ �[0m| 2.98G/11.9G�[A 11%|�[34m█████▎ �[0m|, 0/116 (30.4G 26%|�[34m████████████▉ �[0m| 3.09G/11.9G�[A 11%|�[34m█████▍ �[0m|, 0/116 (30.4G It looks like this normally: 5%|██▌ |, 0/116 (30.4G) 12%|█████▉ | 1.43G/11.9G I'm sure it has to do with the ANSI characters or something and I know it's probably just a simple thing for someone who knows what they are doing to just specify the correct encoding. Even after spending a few hours on it, I just don't know where to begin looking. Any Ideas?
  15. Ich sehe es aus irgendeinem Grund immer noch: Vielleicht ist es immer noch in meinem Cache oder so. Aber ich denke, es spielt eigentlich keine Rolle, solange es niemanden mehr beeinflusst.
  16. Ich habe es aus dem Community-Anwendungen-Store heruntergeladen, daher haben sie es möglicherweise entfernt. Das würde die mangelnden Informationen darüber erklären. Ich war überrascht, dass es dort war, nachdem ich festgestellt hatte, wie fehlerhaft es ist.
  17. Dieses Plugin ist völlig fehlerhaft. Der Support-Link führt nicht zur richtigen Webseite. Die Einstellungsseite ist leer und sperrt die Webbenutzeroberfläche. Die Deinstallation funktioniert nicht. Es sollte nicht einmal in der Beta-Phase sein. Es gibt keine Support-Seite.
  18. Does anyone know of any connectors for US banks? It seems like there are lots of pre-configured for EU but you have to manually create your own for others.
  19. I found it pretty easy to use with the Docker Compose plugin: compose: version: '3.3' # # The Firefly III Data Importer will ask you for the Firefly III URL and a "Client ID". # You can generate the Client ID at http://localhost/profile (after registering) # The Firefly III URL is: http://app:8080 # # Other URL's will give 500 | Server Error # services: app: image: fireflyiii/core:latest hostname: app container_name: firefly_iii_core networks: - firefly_iii restart: always volumes: - firefly_iii_upload:/var/www/html/storage/upload env_file: .env ports: - '8365:8080' depends_on: - db db: image: mariadb hostname: db container_name: firefly_iii_db networks: - firefly_iii restart: always env_file: .db.env volumes: - firefly_iii_db:/var/lib/mysql importer: image: fireflyiii/data-importer:latest hostname: importer restart: always container_name: firefly_iii_importer networks: - firefly_iii ports: - '8366:8080' depends_on: - app env_file: .importer.env cron: # # To make this work, set STATIC_CRON_TOKEN in your .env file or as an environment variable and replace REPLACEME below # The STATIC_CRON_TOKEN must be *exactly* 32 characters long # image: alpine container_name: firefly_iii_cron restart: always command: sh -c "echo \"0 3 * * * wget -qO- http://app:8365/api/v1/cron/REPLACEME\" | crontab - && crond -f -L /dev/stdout" networks: - firefly_iii volumes: firefly_iii_upload: firefly_iii_db: networks: firefly_iii: driver: bridge env: # You can leave this on "local". If you change it to production most console commands will ask for extra confirmation. # Never set it to "testing". APP_ENV=local # Set to true if you want to see debug information in error screens. APP_DEBUG=false # This should be your email address. # If you use Docker or similar, you can set this variable from a file by using SITE_OWNER_FILE # The variable is used in some errors shown to users who aren't admin. [email protected] # The encryption key for your sessions. Keep this very secure. # Change it to a string of exactly 32 chars or use something like `php artisan key:generate` to generate it. # If you use Docker or similar, you can set this variable from a file by using APP_KEY_FILE # # Avoid the "#" character in your APP_KEY, it may break things. # APP_KEY=SomeRandomStringOf32CharsExactly # Firefly III will launch using this language (for new users and unauthenticated visitors) # For a list of available languages: https://github.com/firefly-iii/firefly-iii/tree/main/resources/lang # # If text is still in English, remember that not everything may have been translated. DEFAULT_LANGUAGE=en_US # The locale defines how numbers are formatted. # by default this value is the same as whatever the language is. DEFAULT_LOCALE=equal # Change this value to your preferred time zone. # Example: Europe/Amsterdam # For a list of supported time zones, see https://en.wikipedia.org/wiki/List_of_tz_database_time_zones TZ=Europe/Amsterdam # TRUSTED_PROXIES is a useful variable when using Docker and/or a reverse proxy. # Set it to ** and reverse proxies work just fine. TRUSTED_PROXIES= # The log channel defines where your log entries go to. # Several other options exist. You can use 'single' for one big fat error log (not recommended). # Also available are 'syslog', 'errorlog' and 'stdout' which will log to the system itself. # A rotating log option is 'daily', creates 5 files that (surprise) rotate. # A cool option is 'papertrail' for cloud logging # Default setting 'stack' will log to 'daily' and to 'stdout' at the same time. LOG_CHANNEL=stack # # Used when logging to papertrail: # PAPERTRAIL_HOST= PAPERTRAIL_PORT= # Log level. You can set this from least severe to most severe: # debug, info, notice, warning, error, critical, alert, emergency # If you set it to debug your logs will grow large, and fast. If you set it to emergency probably # nothing will get logged, ever. APP_LOG_LEVEL=notice # Audit log level. # Set this to "emergency" if you dont want to store audit logs, leave on info otherwise. AUDIT_LOG_LEVEL=info # Database credentials. Make sure the database exists. I recommend a dedicated user for Firefly III # For other database types, please see the FAQ: https://docs.firefly-iii.org/firefly-iii/faq/self-hosted/#i-want-to-use-sqlite # If you use Docker or similar, you can set these variables from a file by appending them with _FILE # Use "pgsql" for PostgreSQL # Use "mysql" for MySQL and MariaDB. # Use "sqlite" for SQLite. DB_CONNECTION=mysql DB_HOST=db DB_PORT=3306 DB_DATABASE=firefly DB_USERNAME=firefly DB_PASSWORD=secret_firefly_password # leave empty or omit when not using a socket connection DB_SOCKET= # MySQL supports SSL. You can configure it here. # If you use Docker or similar, you can set these variables from a file by appending them with _FILE MYSQL_USE_SSL=false MYSQL_SSL_VERIFY_SERVER_CERT=true # You need to set at least of these options MYSQL_SSL_CAPATH=/etc/ssl/certs/ MYSQL_SSL_CA= MYSQL_SSL_CERT= MYSQL_SSL_KEY= MYSQL_SSL_CIPHER= # PostgreSQL supports SSL. You can configure it here. # If you use Docker or similar, you can set these variables from a file by appending them with _FILE PGSQL_SSL_MODE=prefer PGSQL_SSL_ROOT_CERT=null PGSQL_SSL_CERT=null PGSQL_SSL_KEY=null PGSQL_SSL_CRL_FILE=null # more PostgreSQL settings PGSQL_SCHEMA=public # If you're looking for performance improvements, you could install memcached or redis CACHE_DRIVER=file SESSION_DRIVER=file # If you set either of the options above to 'redis', you might want to update these settings too # If you use Docker or similar, you can set REDIS_HOST_FILE, REDIS_PASSWORD_FILE or # REDIS_PORT_FILE to set the value from a file instead of from an environment variable # can be tcp, unix or http REDIS_SCHEME=tcp # use only when using 'unix' for REDIS_SCHEME. Leave empty otherwise. REDIS_PATH= # use only when using 'tcp' or 'http' for REDIS_SCHEME. Leave empty otherwise. REDIS_HOST=127.0.0.1 REDIS_PORT=6379 # Use only with Redis 6+ with proper ACL set. Leave empty otherwise. REDIS_USERNAME= REDIS_PASSWORD= # always use quotes and make sure redis db "0" and "1" exists. Otherwise change accordingly. REDIS_DB="0" REDIS_CACHE_DB="1" # Cookie settings. Should not be necessary to change these. # If you use Docker or similar, you can set COOKIE_DOMAIN_FILE to set # the value from a file instead of from an environment variable # Setting samesite to "strict" may give you trouble logging in. COOKIE_PATH="/" COOKIE_DOMAIN= COOKIE_SECURE=false COOKIE_SAMESITE=lax # If you want Firefly III to email you, update these settings # For instructions, see: https://docs.firefly-iii.org/firefly-iii/advanced-installation/email/#email # If you use Docker or similar, you can set these variables from a file by appending them with _FILE MAIL_MAILER=log MAIL_HOST=null MAIL_PORT=2525 [email protected] MAIL_USERNAME=null MAIL_PASSWORD=null MAIL_ENCRYPTION=null MAIL_SENDMAIL_COMMAND= # Other mail drivers: # If you use Docker or similar, you can set these variables from a file by appending them with _FILE MAILGUN_DOMAIN= MAILGUN_SECRET= # If you are on EU region in mailgun, use api.eu.mailgun.net, otherwise use api.mailgun.net # If you use Docker or similar, you can set this variable from a file by appending it with _FILE MAILGUN_ENDPOINT=api.mailgun.net # If you use Docker or similar, you can set these variables from a file by appending them with _FILE MANDRILL_SECRET= SPARKPOST_SECRET= # Firefly III can send you the following messages. SEND_ERROR_MESSAGE=true # These messages contain (sensitive) transaction information: SEND_REPORT_JOURNALS=true # Set this value to true if you want to set the location of certain things, like transactions. # Since this involves an external service, it's optional and disabled by default. ENABLE_EXTERNAL_MAP=false # Set this value to true if you want Firefly III to download currency exchange rates # from the internet. These rates are hosted by the creator of Firefly III inside # an Azure Storage Container. # Not all currencies may be available. Rates may be wrong. ENABLE_EXTERNAL_RATES=false # The map will default to this location: MAP_DEFAULT_LAT=51.983333 MAP_DEFAULT_LONG=5.916667 MAP_DEFAULT_ZOOM=6 # # Firefly III authentication settings # # # Firefly III supports a few authentication methods: # - 'web' (default, uses built in DB) # - 'remote_user_guard' for Authelia etc # Read more about these settings in the documentation. # https://docs.firefly-iii.org/firefly-iii/advanced-installation/authentication # # LDAP is no longer supported :( # AUTHENTICATION_GUARD=web # # Remote user guard settings # AUTHENTICATION_GUARD_HEADER=REMOTE_USER AUTHENTICATION_GUARD_EMAIL= # # Firefly III generates a basic keypair for your OAuth tokens. # If you want, you can overrule the key with your own (secure) value. # It's also possible to set PASSPORT_PUBLIC_KEY_FILE or PASSPORT_PRIVATE_KEY_FILE # if you're using Docker secrets or similar solutions for secret management # PASSPORT_PRIVATE_KEY= PASSPORT_PUBLIC_KEY= # # Extra authentication settings # CUSTOM_LOGOUT_URL= # You can disable the X-Frame-Options header if it interferes with tools like # Organizr. This is at your own risk. Applications running in frames run the risk # of leaking information to their parent frame. DISABLE_FRAME_HEADER=false # You can disable the Content Security Policy header when you're using an ancient browser # or any version of Microsoft Edge / Internet Explorer (which amounts to the same thing really) # This leaves you with the risk of not being able to stop XSS bugs should they ever surface. # This is at your own risk. DISABLE_CSP_HEADER=false # If you wish to track your own behavior over Firefly III, set valid analytics tracker information here. # Nobody uses this except for me on the demo site. But hey, feel free to use this if you want to. # Do not prepend the TRACKER_URL with http:// or https:// # The only tracker supported is Matomo. # You can set the following variables from a file by appending them with _FILE: TRACKER_SITE_ID= TRACKER_URL= # # Firefly III supports webhooks. These are security sensitive and must be enabled manually first. # ALLOW_WEBHOOKS=false # # The static cron job token can be useful when you use Docker and wish to manage cron jobs. # 1. Set this token to any 32-character value (this is important!). # 2. Use this token in the cron URL instead of a user's command line token that you can find in /profile # # For more info: https://docs.firefly-iii.org/firefly-iii/advanced-installation/cron/ # # You can set this variable from a file by appending it with _FILE # STATIC_CRON_TOKEN= # You can fine tune the start-up of a Docker container by editing these environment variables. # Use this at your own risk. Disabling certain checks and features may result in lots of inconsistent data. # However if you know what you're doing you can significantly speed up container start times. # Set each value to true to enable, or false to disable. # Set this to true to build all locales supported by Firefly III. # This may take quite some time (several minutes) and is generally not recommended. # If you wish to change or alter the list of locales, start your Docker container with # `docker run -v locale.gen:/etc/locale.gen -e DKR_BUILD_LOCALE=true` # and make sure your preferred locales are in your own locale.gen. DKR_BUILD_LOCALE=false # Check if the SQLite database exists. Can be skipped if you're not using SQLite. # Won't significantly speed up things. DKR_CHECK_SQLITE=true # Run database creation and migration commands. Disable this only if you're 100% sure the DB exists # and is up to date. DKR_RUN_MIGRATION=true # Run database upgrade commands. Disable this only when you're 100% sure your DB is up-to-date # with the latest fixes (outside of migrations!) DKR_RUN_UPGRADE=true # Verify database integrity. Includes all data checks and verifications. # Disabling this makes Firefly III assume your DB is intact. DKR_RUN_VERIFY=true # Run database reporting commands. When disabled, Firefly III won't go over your data to report current state. # Disabling this should have no impact on data integrity or safety but it won't warn you of possible issues. DKR_RUN_REPORT=true # Generate OAuth2 keys. # When disabled, Firefly III won't attempt to generate OAuth2 Passport keys. This won't be an issue, IFF (if and only if) # you had previously generated keys already and they're stored in your database for restoration. DKR_RUN_PASSPORT_INSTALL=true # Leave the following configuration vars as is. # Unless you like to tinker and know what you're doing. APP_NAME=FireflyIII BROADCAST_DRIVER=log QUEUE_DRIVER=sync CACHE_PREFIX=firefly PUSHER_KEY= IPINFO_TOKEN= PUSHER_SECRET= PUSHER_ID= DEMO_USERNAME= DEMO_PASSWORD= FIREFLY_III_LAYOUT=v1 # # If you have trouble configuring your Firefly III installation, DON'T BOTHER setting this variable. # It won't work. It doesn't do ANYTHING. Don't believe the lies you read online. I'm not joking. # This configuration value WILL NOT HELP. # # Notable exception to this rule is Synology, which, according to some users, will use APP_URL to rewrite stuff. # # This variable is ONLY used in some of the emails Firefly III sends around. Nowhere else. # So when configuring anything WEB related this variable doesn't do anything. Nothing # # If you're stuck I understand you get desperate but look SOMEWHERE ELSE. # APP_URL=http://localhost
  20. To clarify, NIFI_WEB_HTTP_PORT needs to be the same as the container port for "Web Interface Port", which is 8080 by default. I had some issues with this until I realized that. I also made it a port initially instead of a variable because I'm an idiot, or was tired, or both. So if you create the variable NIFI_WEB_HTTP_PORT and give it the value of 8080 you should be good, regardless of whether or not you need to change the host port for "Web Interface Port" if 8080 is already being used for the host. As for the config, it should be /opt/nifi/nifi-current but that causes issues with some files not being created. Still working on that one.
  21. I put this off for a while because I had more important things but I am still having this issue. I'm pretty sure it's just taking a long time to allocate all the RAM and other resources but using less RAM isn't really a solution. Anyone have any ideas? What I am currently seeing as the solution is to re-compile qemu with PREEMPT_NONE=y and CONFIG_VOLUNTARY_PREEMPTP=Y
  22. Is it an NMVe drive? With those I believe you have to pass through the controller instead. Otherwise I would try mounting it in Unassigned Devices to see if it shows up in the list of drives.
  23. You have to run `apt-get update` first before you run `apt-get install dbus-x11`. That will update the list of what packages are available to install, which is why it can't find it. Sorry, it's kind of habitual and standard practice to do that first so I don't always remember to explicitly say that. FYI, I'm not sure how much longer I will support this. For one, Docker Hub is requiring payment for features that used to be free, which means I may have to figure out an alternative and I'm not sure I want to spend time on it because I don't use rmlint anymore. It's only been pretty solid, as I've had only three support requests in over two years. Additionally, I've been working on a new plugin that will be a replacement for this. It's getting close to being good enough for a beta release so keep an eye out in you are interested.
  24. I did realize just a few minutes ago that Disk Utilities didn't exist. I didn't realize it was a custom section created by the pre-clear plugin. The problem I had doing it that way is that they are now separate pages. I was hoping to keep the tabs so once the user gets to the page they don't have to click through the UI a bunch to go between "main" and "settings". I did just find a bit of a trick to get a tabbed page to appear in both "Settings" and "Tools" though. Since it goes off of the name of the page file I copied "Dedupe.page" as "Dedupe .page" and changed "DiskUtilities" to "Utilities". The whitespace gets stripped at the end of the file name. I don't think there is a way to have it go to anything but the first tab though and I'm trying to get the link in the "Settings" page to go to the "Settings" tab, which is second.
×
×
  • Create New...